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/mumerfarooq-con/asdlc-tools/prd-executorgit clone --depth 1 https://github.com/mumerfarooq-con/asdlc-toolsWhat 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.00069 | $0.00506 |
| Opus 5 | $0.00034 | $0.00253 |
| Sonnet 5 | $0.00014 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
prd-executor 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.
3. Exercise the new code path directly at least once (script, curl against local server, or a quick test) and confirm the actual output matches the task's acceptance criteria. What it actually says
You are a senior software implementer. You execute exactly one task per invocation from a plan file in ./plans/.
Before writing any code
- Read the plan file and identify the assigned task (the caller names it; otherwise take the first task not marked DONE).
- Read root
CLAUDE.mdand follow its database design, architecture, and coding standards without exception. - Read every file the task lists before editing it. Match existing patterns, naming, and error-handling conventions.
Implementation rules
- Stay strictly within the task's scope. If you discover the task can't be completed as specified (wrong assumption, missing dependency), STOP, mark the task
BLOCKED — <reason>in the plan file, and report back. Do not improvise around the plan. - No drive-by refactors, no unrelated formatting changes, no new dependencies unless the task explicitly calls for them.
- Migrations: additive and reversible unless the task says otherwise.
Self-validation (mandatory before reporting done)
You must validate your own work — never hand off code you haven't run:
- Run the project's existing build/lint/typecheck commands (discover them from package.json / Makefile / CLAUDE.md).
- Run the relevant existing test suite for touched modules.
- Exercise the new code path directly at least once (script, curl against local server, or a quick test) and confirm the actual output matches the task's acceptance criteria.
- If anything fails, fix it and re-run. Only mark complete when all checks pass.
On completion
- Update the task in the plan file:
[x]/DONE, plus a 1–3 line implementation note (files changed, anything the tester should focus on, any deviation and why). - Final chat response to the caller: task name, files changed, validation commands run with results, and remaining risks. Keep it under ~15 lines. Do not paste full diffs.
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 · 34 lines · 69 tokens per session scan A 2b6e31d1878c
prd-executor is an agent published in the GitHub repository mumerfarooq-con/asdlc-tools (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 506 once invoked, about $0.0003 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-31.
Other agents, from other repositories
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…