Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/agent-field/swe-af/delegate-issuenpx skills add Agent-Field/SWE-AF --skill delegate-issuegit clone --depth 1 https://github.com/Agent-Field/SWE-AFWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00082 | $0.01182 |
| Opus 5 | $0.00041 | $0.00591 |
| Sonnet 5 | $0.00016 | $0.00236 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
delegate-issue scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s ${AGENTFIELD_SERVER:-http://localhost:8080}/api/v1/nodes | grep -o '"swe-[a-z-]*"' | sort -u How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegate scoped issues to SWE-AF
You are the main harness. SWE-AF is the sub-harness: it implements one fully-scoped issue per call on an isolated branch, using cheap models, and hands the branch back. You keep planning, merging, review, and CI.
When to delegate (and when not to)
Delegate an issue only when ALL of these hold:
- The change is fully specified: you can name the files, the behavior, and the acceptance criteria without the sub-harness needing to plan anything.
- It is independent of your other in-flight edits (no shared files with another delegation or with your own uncommitted work).
- The repo is reachable by the SWE-AF node (same machine or shared volume) and has at least one commit.
Do NOT delegate: vague feature requests (use swe-planner.build instead),
changes to files you are editing yourself right now, or anything whose spec
you'd have to guess. Garbage spec in → garbage branch out.
Preflight (once per session)
# Control plane up and the node registered?
curl -s ${AGENTFIELD_SERVER:-http://localhost:8080}/api/v1/nodes | grep -o '"swe-[a-z-]*"' | sort -u
Pick the node (swe-planner, swe-fast, or the -go twins — the
implement_issue surface is identical). If an X-API-Key is configured for
the control plane, add -H "X-API-Key: $AGENTFIELD_API_KEY" to every curl.
Compose the issue
Write the spec from YOUR context — the whole point is that the sub-harness
skips planning. Required: title, description. Strongly recommended:
acceptance_criteria (verifier checks these), files_to_modify /
files_to_create, testing_strategy. Set needs_deeper_qa: true only for
risky/interface-heavy changes (doubles the review cost per iteration).
Commit (or at least be aware of) your local state first: the issue branch is created from the committed base, so your uncommitted edits are invisible to it.
Fire the delegation (async, never sync)
curl -s -X POST ${AGENTFIELD_SERVER:-http://localhost:8080}/api/v1/execute/async/swe-planner.implement_issue \
-H "Content-Type: application/json" \
-d @issue.json
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 117 lines · 82 tokens per session scan A 678bc4256b3e
delegate-issue is a skill published in the GitHub repository Agent-Field/SWE-AF (989 stars, last pushed 9d ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,182 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-reproduce-feature
Use when reproducing an existing Codex or Claude Code feature in Qwen Code or another agent CLI by choosing a reference agent, capturing HTTP request bodies, prompts, tool/function schemas, terminal output, and then implementing the matching behavior in the target repo.
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
delegate
Strategic delegation for multi-step coding, research, or verification work. Use when a task can be split into parent reasoning plus focused sub-agent execution through the agent tool.
skill-creator
Create or improve codewhale skills. Use when the user wants a new skill, wants to update an existing skill, or needs guidance on when a skill should be a skill versus MCP, hooks, tools, or a plugin scaffold.
plugin-creator
Scaffold a local Codewhale plugin bundle with a versioned manifest, namespaced Skills, and an explicit trust review.
mcp-builder
Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.