Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add alexsds/ade-workflow/plugin install adeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/alexsds/ade-workflow/ade-generator)<a href="https://agentmods.dev/agents/alexsds/ade-workflow/ade-generator"><img src="https://agentmods.dev/badge/agents/alexsds/ade-workflow/ade-generator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/alexsds/ade-workflow/ade-generator"><img src="https://agentmods.dev/badge/agents/alexsds/ade-workflow/ade-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00198 | $0.00395 |
| Opus 5.5 | $0.00079 | $0.00158 |
| Sonnet 5.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 1mo 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.
- 1mo 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 6mo ago), licensed MIT. It adds 198 tokens to every session and 395 once invoked, about $0.0008 per session on Opus 5.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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.