
codeagent
Execute codeagent-wrapper for multi-backend AI code tasks. Supports Codex, Claude, Gemini, and OpenCode backends with agent presets, skill injection, file references (@syntax), worktree isolation, parallel execution, and structured output.
- Installs
- 216
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/stellarlinkco/myclaude --skill codeagent- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads codeagent automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Codeagent Wrapper Integration
Overview
Execute codeagent-wrapper commands with pluggable AI backends (Codex, Claude, Gemini, OpenCode), agent presets, auto-detected skill injection, and parallel task orchestration. Default to background execution, and prefer --parallel whenever work can be split into independent tasks.
When to Use
- Complex code analysis requiring deep understanding
- Large-scale refactoring across multiple files
- Multi-agent orchestration (explore → design → implement → review)
- Automated code generation with backend/agent selection
- Parallel task execution with dependency management
Quick Reference
codeagent-wrapper [flags] <task|-> [workdir]
codeagent-wrapper [flags] resume <session_id> <task|-> [workdir]
codeagent-wrapper --parallel [flags] < tasks_config
CLI Flags
| Flag | Description | Default |
|---|---|---|
--backend <name> | Backend: codex, claude, gemini, opencode | codex |
--agent <name> | Agent preset (from models.json or agents/ dir) | none |
--model <name> | Model override for any backend | backend default |
--skills <names> | Comma-separated skill names to inject | auto-detected |
--reasoning-effort <level> | Reasoning level: low, medium, high | backend default |
--prompt-file <path> | Custom prompt file (restricted to ~/.claude or ~/.codeagent/agents/) | none |
--output <path> | Write structured JSON output to file | none |
--worktree | Execute in isolated git worktree (branch: do/{task_id}) | false |
--skip-permissions | Skip Claude backend permission prompts | false |
--parallel | Enable parallel task execution from stdin | false |
--full-output | Include full messages in parallel output (default: summary) | false |
--config <path> | Config file path | ~/.codeagent/config.* |
--cleanup | Clean up old logs and exit | — |
-v, --version | Print version and exit | — |
Backends
| Backend | Flag | Best For |
|---|---|---|
| Codex | --backend codex (default) | Deep code analysis, complex logic, algorithm optimization, large-scale refactoring |
| Claude | --backend claude | Documentation, prompt engineering, clear-requirement features |
| Gemini | --backend gemini | UI/UX prototyping, design system implementation |
| OpenCode | --backend opencode | Lightweight tasks, minimal feature set |
Agent Presets
Agent presets bundle backend, model, prompt, and tool control into a reusable name. Use --agent <name> to select.
Sources (checked in order):
~/.codeagent/models.json→agents.<name>object~/.codeagent/agents/<name>.md→ markdown file becomes the prompt
Agent config fields (in models.json):
{
"agents": {
"develop": {
"backend": "codex",
"model": "gpt-4.1",
"prompt_file": "~/.codeagent/prompts/develop.md",
"reasoning": "high",
"yolo": true,
"allowed_tools": ["Read", "Write", "Bash"],
"disallowed_tools": ["WebFetch"]
}
}
}
Common agent presets:
| Agent | Purpose | Read-Only |
|---|---|---|
code-explorer | Trace code, map architecture, find patterns | Yes |
code-architect | Design approaches, file plans, build sequences | Yes |
code-reviewer | Review for bugs, simplicity, conventions | Yes |
develop | Implement code, run tests, make changes | No |
Skill Injection
Auto-Detection
When --skills is not specified, skills are auto-detected from the working directory:
| Detected Files | Injected Skills |
|---|---|
go.mod / go.sum | golang-base-practices |
Cargo.toml | rust-best-practices |
pyproject.toml / setup.py / requirements.txt | python-best-practices |
package.json | vercel-react-best-practices, frontend-design |
vue.config.js / vite.config.ts / nuxt.config.ts | vue-web-app |
Manual Override
codeagent-wrapper --agent develop --skills golang-base-practices,frontend-design - . <<'EOF'
Implement full-stack feature...
EOF
Skills are loaded from ~/.claude/skills/{name}/SKILL.md, stripped of YAML frontmatter, and injected into the task prompt.
Usage Patterns
Single Task (HEREDOC recommended)
codeagent-wrapper --backend codex - [workdir] <<'EOF'
<task content here>
EOF
Default execution mode is background. Run in foreground only when the next step requires the full response immediately.
When running in foreground, codeagent-wrapper emits liveness frames on stdout before the final answer:
[codeagent-progress] status=started ...
[codeagent-progress] status=streaming ...
[codeagent-progress] status=running ...
[codeagent-progress] status=completed ...
Treat these lines as progress only. Do not conclude "no data returned" and do not start doing the task yourself while progress frames are still arriving.
With Agent Preset
codeagent-wrapper --agent develop --skills golang-base-practices - . <<'EOF'
Implement the authentication middleware following existing patterns.
EOF
Simple Task (short prompts only)
codeagent-wrapper --backend codex "simple task description" [workdir]
Auto-stdin detection: When task length exceeds 800 characters or contains special characters (\n, \, ", ', `, $), stdin mode is used automatically. Use - to force stdin mode explicitly.
Resume Session
codeagent-wrapper --backend codex resume <session_id> - <<'EOF'
<follow-up task>
EOF
# Or with agent preset
codeagent-wrapper --agent develop resume <session_id> - <<'EOF'
<follow-up task>
EOF
Worktree Isolation
Execute in an isolated git worktree to keep changes separate from the main branch:
codeagent-wrapper --agent develop --worktree - . <<'EOF'
Implement feature in isolation...
EOF
Rules:
- Read-only agents (code-explorer, code-architect, code-reviewer) do NOT need worktree
- Only
developagent needs worktree when making changes
Parallel Execution
Use --parallel by default for multi-step or multi-agent work. Fall back to single-task mode only when the work is truly linear or the next step depends on the full output of the current task.
Task Config Format
codeagent-wrapper --parallel <<'EOF'
---TASK---
id: <unique_id>
agent: <agent_name>
workdir: <path>
backend: <name>
model: <model_name>
reasoning_effort: <low|medium|high>
skills: <skill1>, <skill2>
dependencies: <id1>, <id2>
session_id: <id>
skip_permissions: true|false
worktree: true|false
---CONTENT---
<task content>
EOF
Task header fields (all optional except id):
| Field | Description |
|---|---|
id | Unique task identifier (required) |
agent | Agent preset name |
workdir | Working directory |
backend | Override global backend |
model | Override model |
reasoning_effort | Reasoning level |
skills | Comma-separated skill names |
dependencies | Comma-separated task IDs that must complete first |
session_id | Resume a previous session |
skip_permissions | Skip permission prompts (Claude backend) |
worktree | Execute in git worktree |
Multi-Agent Orchestration Example
codeagent-wrapper --parallel <<'EOF'
---TASK---
id: p1_architecture
agent: code-explorer
workdir: .
---CONTENT---
Map architecture for the authentication subsystem. Return: module map + key files with line numbers.
---TASK---
id: p1_conventions
agent: code-explorer
workdir: .
---CONTENT---
Identify testing patterns, conventions, config. Return: test commands + file locations.
---TASK---
id: p2_design
agent: code-architect
workdir: .
dependencies: p1_architecture, p1_conventions
---CONTENT---
Design minimal-change implementation plan based on architecture analysis.
---TASK---
id: p3_backend
agent: develop
workdir: .
skills: golang-base-practices
dependencies: p2_design
---CONTENT---
Implement backend changes following the design plan.
---TASK---
id: p3_frontend
agent: develop
workdir: .
skills: vercel-react-best-practices,frontend-design
dependencies: p2_design
---CONTENT---
Implement frontend changes following the design plan.
---TASK---
id: p4_review
agent: code-reviewer
workdir: .
dependencies: p3_backend, p3_frontend
---CONTENT---
Review all changes for correctness, edge cases, and KISS compliance.
Classify each issue as BLOCKING or MINOR.
EOF
Dependency Resolution
- Tasks are topologically sorted (Kahn's algorithm)
- Circular dependencies are detected and reported
- Failed parent tasks cause dependent tasks to be skipped
- Independent tasks at the same level run concurrently
Output Modes
Summary (default): Structured report per task with extracted fields:
=== Execution Report ===
3 tasks | 2 passed | 1 failed
### task_id PASS 92%
Did: Brief description of work done
Files: file1.ts, file2.ts
Tests: 12 passed
Log: /tmp/codeagent-xxx.log
### task_id FAIL
Exit code: 1
Error: Assertion failed
Detail: Expected status 200 but got 401
Log: /tmp/codeagent-zzz.log
Full output (--full-output): Complete task messages included. Use only for debugging specific failures.
Structured JSON Output
codeagent-wrapper --parallel --output results.json <<'EOF'
...
EOF
Produces:
{
"results": [
{
"task_id": "task_1",
"exit_code": 0,
"message": "...",
"session_id": "...",
"coverage": "92%",
"files_changed": ["file.ts"],
"tests_passed": 12,
"log_path": "/tmp/..."
}
],
"summary": { "total": 3, "success": 2, "failed": 1 }
}
Return Format
Single task output:
Agent response text here...
---
SESSION_ID: 019a7247-ac9d-71f3-89e2-a823dbd8fd14
Environment Variables
| Variable | Description | Default |
|---|---|---|
CODEAGENT_SKIP_PERMISSIONS | Skip Claude backend permission prompts (true/false) | true |
CODEX_BYPASS_SANDBOX | Control Codex sandbox bypass (true/false) | true |
CODEAGENT_MAX_PARALLEL_WORKERS | Max concurrent parallel workers (0=unlimited, max 100) | 0 |
CODEAGENT_TMPDIR | Custom temp directory for executable scripts | system temp |
CODEAGENT_ASCII_MODE | Use ASCII symbols (PASS/WARN/FAIL) instead of Unicode | false |
Config file: Supports ~/.codeagent/config.(yaml|yml|json|toml) with the same keys as CLI flags (kebab-case). Env vars use CODEAGENT_ prefix with underscores.
Exit Codes
| Code | Meaning |
|---|---|
0 | Success |
1 | General error (missing args, failed task) |
127 | Backend command not found |
130 | Interrupted (Ctrl+C) |
Invocation Pattern
Single Task:
Bash tool parameters:
- command: codeagent-wrapper --agent <agent> --skills <skills> - [workdir] <<'EOF'
<task content>
EOF
- background: true
- description: <brief description>
Parallel Tasks:
Bash tool parameters:
- command: codeagent-wrapper --parallel <<'EOF'
---TASK---
id: task_id
agent: <agent>
workdir: /path
skills: <skill1>, <skill2>
dependencies: dep1, dep2
---CONTENT---
task content
EOF
- background: true
- description: <brief description>
Critical Rules
NEVER kill codeagent processes. Long-running tasks are normal. Default to background execution and inspect progress instead of blocking on the command.
-
Check task status via log file:
tail -f /tmp/claude/<workdir>/tasks/<task_id>.output -
Prefer wrapper progress frames over ad-hoc log scraping: If stdout is still emitting
[codeagent-progress] ..., the task is alive and has not stalled. -
Check process without killing:
ps aux | grep codeagent-wrapper | grep -v grep
Why: Killing wastes API costs and loses progress.
Tool Control (Claude Backend)
When using Claude backend with agent presets, control available tools:
{
"agents": {
"safe-develop": {
"backend": "claude",
"allowed_tools": ["Read", "Write", "Bash", "Grep", "Glob"],
"disallowed_tools": ["WebFetch", "WebSearch"]
}
}
}
Passed as --allowedTools and --disallowedTools to Claude CLI. Explicit enumeration only (no wildcards).
FAQ
What does the codeagent skill do?
Execute codeagent-wrapper for multi-backend AI code tasks. Supports Codex, Claude, Gemini, and OpenCode backends with agent presets, skill injection, file references (@syntax), worktree isolation, parallel execution, and structured output.
How do I install codeagent?
Run npx skills add https://github.com/stellarlinkco/myclaude --skill codeagent in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/codeagent/ (personal) or .claude/skills/codeagent/ (project).
Which AI agents can use codeagent?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is codeagent safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains codeagent?
It is published by stellarlinkco in stellarlinkco/myclaude. It has 216 recorded installs.
More from stellarlinkco/myclaude
product-requirements
stellarlinkco/myclaude
Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.
test-cases
stellarlinkco/myclaude
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
prototype-prompt-generator
stellarlinkco/myclaude
Open the skill to read its SKILL.md instructions.
browser
stellarlinkco/myclaude
Open the skill to read its SKILL.md instructions.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.