How do I install the Authentication Flows Devforge skill?

Run npx skillmds@latest add construct-ai-primary/authentication-flows-devforge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Authentication Flows Devforge safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Authentication Flows Devforge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Authentication Flows Devforge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Authentication Flows Devforge?

Construct-AI-primary (@construct-ai-primary) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Authentication Flows Devforge by construct-ai-primary

Name: Authentication Flows Devforge
Rating: 4.2 (5 reviews)
Author: Construct-AI-primary

Authentication Flows Devforge

Use when authentication issues occur including OAuth to API key migration, session caching problems, CLI auth in authenticated deployment mode, or agent 401 errors. Handles Anthropic OAuth expiration, API key configuration, and auth token refresh.

Construct-AI-primary Updated Sep 8, 2026 0 repo stars

File contents

Authentication Flows - DevForge AI

Overview

Handles authentication and authorization issues in the Paperclip codebase. Resolves OAuth-to-API-key migration issues, session caching problems, CLI authentication in authenticated deployment mode, and agent run 401 errors caused by stale auth tokens.

When to Use

When agents return 401 with "OAuth token has expired" after API key is configured
When CLI commands fail with "Unauthorized" in authenticated deployment mode
When session ID is reused across runs with stale OAuth tokens
When deploymentMode: "authenticated" breaks CLI heartbeat/agent-list commands
Don't use when: It's an API permissions issue (use gatekeeper-devforge-access-control)

Core Procedures

Auth Migration Workflow

Identify Auth Method - Check config.json for llm.provider, llm.apiKey, OAuth settings
Check Session Cache - Look for cached OAuth sessions in instance data
Clear Stale Sessions - Remove cached auth sessions that reference expired tokens
Verify API Key - Confirm API key is correctly set and valid via doctor check
Test Agent Run - Trigger agent run and verify API key is used (not OAuth)
CLI Auth Support - Add email/password or session token support for authenticated mode

Common Auth Issues

OAuth session cached in ~/.paperclip/instances/*/sessions/ — clear to force API key use
CLI has no auth credential passing in authenticated mode — needs --email/--password flags
Agent JWT secret not set — causes 401 on all agent runs

Agent Assignment

Primary Agent: devcore-devforge-core-development Company: DevForge AI Role: Authentication Specialist Reports To: devcore-devforge-core-development Backup Agents: gatekeeper-devforge-access-control, interface-devforge-api-integration

Success Metrics

API key auth works immediately after configuration
No OAuth session reuse after API key switch
CLI works in authenticated mode with proper credentials
Agent runs succeed with configured auth method

Error Handling

Error: API key invalid after config Response: Validate key format, check provider, test with direct API call
Error: CLI auth credentials not available Response: Add credential storage, env var support, or interactive prompt

Cross-Team Integration

Gigabrain Tags: devforge, authentication, oauth, api-key, session, cli-auth Related Skills: devcore-devforge-core-development, gatekeeper-devforge-access-control, interface-devforge-api-integration Last Updated: 2026-04-07

---name: authentication-flows-devforgedescription: Use when authentication issues occur including OAuth to API key migration, session caching problems, CLI auth in authenticated deployment mode, or agent 401 errors. Handles Anthropic OAuth expiration, API key configuration, and auth token refresh.---# Authentication Flows - DevForge AI## OverviewHandles authentication and authorization issues in the Paperclip codebase. Resolves OAuth-to-API-key migration issues, session caching problems, CLI authentication in authenticated deployment mode, and agent run 401 errors caused by stale auth tokens.## When to Use- When agents return 401 with "OAuth token has expired" after API key is configured- When CLI commands fail with "Unauthorized" in authenticated deployment mode- When session ID is reused across runs with stale OAuth tokens- When `deploymentMode: "authenticated"` breaks CLI heartbeat/agent-list commands- **Don't use when:** It's an API permissions issue (use gatekeeper-devforge-access-control)## Core Procedures### Auth Migration Workflow1. **Identify Auth Method** - Check config.json for llm.provider, llm.apiKey, OAuth settings2. **Check Session Cache** - Look for cached OAuth sessions in instance data3. **Clear Stale Sessions** - Remove cached auth sessions that reference expired tokens4. **Verify API Key** - Confirm API key is correctly set and valid via doctor check5. **Test Agent Run** - Trigger agent run and verify API key is used (not OAuth)6. **CLI Auth Support** - Add email/password or session token support for authenticated mode### Common Auth Issues- OAuth session cached in `~/.paperclip/instances/*/sessions/` — clear to force API key use- CLI has no auth credential passing in authenticated mode — needs `--email/--password` flags- Agent JWT secret not set — causes 401 on all agent runs## Agent Assignment**Primary Agent:** devcore-devforge-core-development**Company:** DevForge AI**Role:** Authentication Specialist**Reports To:** devcore-devforge-core-development**Backup Agents:** gatekeeper-devforge-access-control, interface-devforge-api-integration## Success Metrics- API key auth works immediately after configuration- No OAuth session reuse after API key switch- CLI works in authenticated mode with proper credentials- Agent runs succeed with configured auth method## Error Handling- **Error:** API key invalid after config **Response:** Validate key format, check provider, test with direct API call- **Error:** CLI auth credentials not available **Response:** Add credential storage, env var support, or interactive prompt## Cross-Team Integration**Gigabrain Tags:** devforge, authentication, oauth, api-key, session, cli-auth**Related Skills:** devcore-devforge-core-development, gatekeeper-devforge-access-control, interface-devforge-api-integration**Last Updated:** 2026-04-07

Frequently asked questions