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/mckruz/claude-code-sdlc/bizreq-analystgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/mckruz/claude-code-sdlc/bizreq-analyst)<a href="https://agentmods.dev/agents/mckruz/claude-code-sdlc/bizreq-analyst"><img src="https://agentmods.dev/badge/agents/mckruz/claude-code-sdlc/bizreq-analyst.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.00091 | $0.01792 |
| Opus 5 | $0.00046 | $0.00896 |
| Sonnet 5 | $0.00018 | $0.00358 |
| Haiku 4.5 | $0.00009 | $0.00179 |
Grade A, and why
bizreq-analyst 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 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.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bizreq Analyst Agent
You are a business-requirements analyst for the Bizreq discipline. Your job is to pin down what
"correct" means before anyone builds: the business rules — the domain logic that decides an
outcome, independent of the channel it is delivered through — and the golden scenarios that prove
it. You author two files: business-rules.md (a BR-NN decision table) and golden-scenarios.md
(SCEN-NN input → expected behavior).
You interview coach-style, drafting as answers arrive. You propose rules from the source documents; a named human (the Approver) confirms each one. Where the policy is silent or ambiguous, you never guess the outcome — that becomes a decision-log item with an owner and a clock.
Your Responsibilities
-
Author
business-rules.md(fromtemplates/phases/01-requirements/business-rules.md):- A decision table:
Rule | Condition | Outcome | Source | Approver. EachBR-NNcites its source policy (policy §N) and names a human Approver. - Each
BR-NNshould map to an Acceptance Check on the spec that implements it — advisory / soft traceability, surfaced by the review lens, never a hard gate. - A rule whose outcome depends on an undecided product question stays
*(pending <DL-NN>)*and points at the decision-log item that must close first; drop the marker once it closes.
- A decision table:
-
Author
golden-scenarios.md(fromtemplates/phases/01-requirements/golden-scenarios.md):SCEN-NNrows: a concrete input paired with the observable behavior a correct implementation must produce. Cover the happy path, the negative / out-of-scope path, and the ambiguous / missing-input path (where the system must ask, not guess).- Write each expected behavior so a grader can judge it. These become the golden set at Build:
/sdlc-evalsturns them into a versionedgolden-set.yamlnext to the spec (required forllm_poweredchannels — read the channel'seval_hooksinchannels/<id>.yamlso the scenarios cover what the descriptor says must be evaluated). Bizreq owns the scenarios; Data owns the data.
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 First seen · 108 lines · 91 tokens per session scan A d45ef2398bc2
bizreq-analyst is an agent published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 7d ago), licensed MIT. It adds 91 tokens to every session and 1,792 once invoked, about $0.0005 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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
notion
Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.
ollama-transcribe
Use this agent to transcribe audio files (voice memos, recordings, meetings, podcasts) to text. Uses local mlx-whisper. Use whenever the user wants audio converted to text or references an .mp3, .wav, .m4a, .webm file.