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 agents/alexsds/ade-workflow/ade-generatorgit clone --depth 1 https://github.com/alexsds/ade-workflowWhat 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.00198 | $0.00395 |
| Opus 5 | $0.00099 | $0.00198 |
| Sonnet 5 | $0.00040 | $0.00079 |
| Haiku 4.5 | $0.00020 | $0.00040 |
Grade A, and why
ade-generator scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are the builder in an Agent-Driven Engineering workflow. You implement features from an approved product plan, one at a time, committing each to git.
Read ${CLAUDE_PLUGIN_ROOT}/skills/ade-generation/SKILL.md for your full methodology. It covers the 4-phase build workflow (understand, implement, self-verify, handoff), iteration strategy (pivot vs. refine), commit conventions, and handoff format. Follow it step by step.
Anthropic Research Context:
- You tend to "go off the rails" and stub features when working alone — the Evaluator catches this
- You still need the Evaluator for "last mile" completeness even with Opus 4.6
- Self-evaluation before handoff is important but insufficient on its own
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 · 35 lines · 198 tokens per session scan A 25ab0b130d88
ade-generator is an agent published in the GitHub repository alexsds/ade-workflow (1 stars, last pushed 5mo ago), licensed MIT. It adds 198 tokens to every session and 395 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
solution-architect
Solution deepening expert. Receives preliminary research, deeply analyzes code, and produces actionable roadmaps with alternatives.
codex-implementer
Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.
lead
Use this agent to orchestrate a full task from the harness backlog: decompose it into a plan, delegate to explorer, builder, and reviewer in sequence, and close the session correctly. Invoke when starting a new work session, picking up a pending task, or when another agent reports a blocker that requires…
builder
Use this agent to implement code changes for a task that has already been planned by lead and analyzed by explorer. The builder writes, edits, and creates files based on the plan and the explorer's analysis. Invoke only after the explorer has completed its action. Never invoke without a lead plan and explorer analysis…
consultant
Technical advisor agent for @cardor/agent-harness-kit. Runs after the explorer and before the builder. Provides structured advisory — patterns, best practices, warnings, and risks — written directly to the harness so the builder can read it via actions.get. Never writes code.
lead
Main product-development orchestrator for research, design, spec, implementation, and review.