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 commands/mumerfarooq-con/asdlc-tools/implement-prdgit 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/commands/mumerfarooq-con/asdlc-tools/implement-prd)<a href="https://agentmods.dev/commands/mumerfarooq-con/asdlc-tools/implement-prd"><img src="https://agentmods.dev/badge/commands/mumerfarooq-con/asdlc-tools/implement-prd.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.00661 |
| Opus 5 | $0.00014 | $0.00331 |
| Sonnet 5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
implement-prd 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are orchestrating work on the PRD at: $ARGUMENTS
Parse the arguments: if --review-only is present, run Retrospective mode; otherwise run Pipeline mode. You coordinate only — route all planning, coding, review, and testing through subagents to keep your context small.
Pipeline mode (fresh PRD implementation)
-
Plan — Invoke
prd-planneron the PRD. Wait for the plan file path and status.- If
STATUS: BLOCKED, surface the open questions to the user and STOP.
- If
-
Execute → Review → Test loop — For each task in dependency order: a. Invoke
prd-executorwith the plan path and task name.- If BLOCKED, surface to the user and pause.
b. Invoke
prd-reviewerin task mode on the same task. - On
REVIEW: CHANGES_REQUESTED, re-invokeprd-executorwith the findings. Max 2 fix attempts, then escalate to the user. c. OnREVIEW: APPROVED, invokeprd-testeron the task. - On
TEST: FAIL, re-invokeprd-executorwith the failure report, then re-run the reviewer ONLY if the fix touched files beyond the original task scope; otherwise go straight back to the tester. Max 2 fix attempts, then escalate. d. OnTEST: PASS, proceed to the next task.
Independent tasks (no shared files, no dependency edge) may execute in parallel; review and test steps still run per task.
- If BLOCKED, surface to the user and pause.
b. Invoke
-
Wrap up — When all tasks are DONE + APPROVED + PASS:
- Run the full test suite once from the main session as a sanity check.
- Summarize: tasks completed, files changed, tests added, review findings deferred (MINORs), anything flagged.
- Suggest a commit message (do not commit unless asked).
Retrospective mode (--review-only, already-completed PRD)
- Invoke
prd-reviewerin retrospective mode with the PRD path (pass the plan file path too if one exists in ./plans/). - Relay the report location (
./plans/<slug>.review.md) and a severity summary (counts of BLOCKER/MAJOR/MINOR). - Do NOT auto-invoke the executor on findings — ask the user whether to:
- turn the "Suggested follow-up tasks" into a fix-up plan via
prd-planner, then run the normal pipeline on it, or - stop here.
- turn the "Suggested follow-up tasks" into a fix-up plan via
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.
- 3d ago First seen · 43 lines · 27 tokens per session scan A 76aa68afc5f9
implement-prd is a command published in the GitHub repository mumerfarooq-con/asdlc-tools (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 661 once invoked, about $0.0001 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 commands, from other repositories
hire-assess-fit
Run a culture-add fit assessment for a candidate (NOT culture-fit). Names what the team currently lacks, names what this candidate adds, runs gap-bridge analysis. Refuses generic "great culture fit" framing — culture-fit reproduces, culture-add expands. Used as a SUPPLEMENT to the structured rubric, never as a…
distill-insights
Distill captures from a window (week / month / quarter) into named frameworks. Applies ≥3-occurrence threshold. Cross-references against Genius Profile. Produces a distillate document and optional Profile evolution proposals.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
triage
Triage review findings one by one — present pending TODOs for user decision (approve, skip, modify).
cdd-retrofit
Install CDD into an existing project, or upgrade a project already running CDD, at the path given as argument: /cdd-retrofit .
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.