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.
git clone --depth 1 https://github.com/mumerfarooq-con/asdlc-toolsWrote 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/mumerfarooq-con/asdlc-tools/prd-executor)<a href="https://agentmods.dev/agents/mumerfarooq-con/asdlc-tools/prd-executor"><img src="https://agentmods.dev/badge/agents/mumerfarooq-con/asdlc-tools/prd-executor/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/mumerfarooq-con/asdlc-tools/prd-executor"><img src="https://agentmods.dev/badge/agents/mumerfarooq-con/asdlc-tools/prd-executor.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.00069 | $0.00809 |
| Opus 5.5 | $0.00028 | $0.00324 |
| Sonnet 5.5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
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 4d 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. How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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). In a stamped plan, tasks are only the ones above the
<!-- asdlc:progress -->line, and a task's status is its latest Progress entry (see "Progress log"). A task whose latest entry isTEST PASSis finished. - 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 (anEXECUTOR BLOCKEDentry in a stamped plan), 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.
Progress log (stamped plans)
A plan is stamped if it has a line <!-- asdlc:progress -->. For a stamped plan:
- Never edit anything above that line: it is what the human approved, and any change voids the approval.
- Never write the progress line yourself;
stampadds it. - Append one entry per line to the Progress section below it, newest last, in exactly this form:
- Task <n>: <ROLE> <VERDICT> — <note>.<ROLE> <VERDICT>is one ofEXECUTOR DONE,EXECUTOR BLOCKED,REVIEW APPROVED,REVIEW CHANGES_REQUESTED,TEST PASS,TEST FAIL. - Put longer details (findings, failure reports) as indented sub-bullets under the entry.
- A task's current status is its latest entry.
REVIEW CHANGES_REQUESTEDandTEST FAILmean the task needs fixing.
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.
- 4d ago Changed · +12 lines cfd52dc104e0
- 1mo 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 5d ago), licensed MIT. It adds 69 tokens to every session and 809 once invoked, about $0.0003 per session on Opus 5.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
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
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…
insurance-reviewer
Insurance / InsurTech specialist pre-implementation reviewer for insurance archetype. Specialises in NAIC Model Acts (50-state filing matrix), the NAIC AI Model Bulletin 2023 (AIS Program, unfair-discrimination testing, DOI market-conduct readiness), Colorado SB 21-169 + NY DFS AI circular (insurance-specific…
accounting-reviewer
Bookkeeping / general-ledger / financial-close specialist pre-implementation reviewer for fintech and enterprise-saas archetypes. Outputs threat model TM-accounting-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
cms-reviewer
CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.
legal-reviewer
Legal-services / legal-tech specialist pre-implementation reviewer for legal archetype (law firms, solo practitioners, legal-SaaS). Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.