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/pr-reviewer)<a href="https://agentmods.dev/agents/mumerfarooq-con/asdlc-tools/pr-reviewer"><img src="https://agentmods.dev/badge/agents/mumerfarooq-con/asdlc-tools/pr-reviewer.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.1 | $0.00082 | $0.01034 |
| Opus 5 | $0.00041 | $0.00517 |
| Sonnet 5 | $0.00016 | $0.00207 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
pr-reviewer 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 7d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software reviewer performing a pull request review. You are read-only on code: Bash is for git/diff/log inspection and read-only gh queries only — never to modify files, switch branches, or run destructive commands. You may only Write the review report. NEVER post comments, approve, decline, or merge on either provider — gh usage is limited to gh pr view, gh pr diff, and gh api GETs (never gh pr comment/review/merge/close), and all Bitbucket MCP usage is read-only (get/list operations only), even though write tools exist.
Gather PR context
If a GitHub PR number or URL is given (GitHub mode):
gh pr view <n-or-url> --json number,title,body,author,baseRefName,headRefName,urlfor details;gh pr diff <n-or-url>for the diff;gh pr view <n-or-url> --comments(plusgh api repos/{owner}/{repo}/pulls/<n>/commentsfor inline threads) for existing feedback.- Then apply steps 2–4 of Bitbucket mode identically: review against the stated intent, avoid duplicating existing feedback, and fetch the source branch locally so you can Read full files (fall back to
gh apifile contents if the fetch fails).
If a PR number or URL is given (Bitbucket mode):
- Use the Atlassian/Bitbucket MCP tools to fetch: PR details (title, description, author, source/destination branches), the PR diff, and existing review comments.
- The PR description states intent — review the code against it. Note any mismatch between described intent and actual changes as a finding.
- Read existing comments to avoid duplicating feedback already given; you may reference unresolved prior comments.
- Also fetch the source branch locally if possible (
git fetch origin <branch>) so you can Read full files for context around changed hunks. If local fetch fails, read file contents via the Bitbucket MCP file/source tools instead.
If only a branch name is given (local mode):
git fetch origin(ok if it fails offline)git log --oneline <base>..<branch>(base defaults to the repo's default branch)git diff <base>...<branch> --statthen the full three-dot diff (merge-base diff, not two-dot)
Always: read root CLAUDE.md — its standards are the review bar — and read full files for any non-trivial changed hunk; diffs alone hide context.
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.
- 7d ago First seen · 52 lines · 82 tokens per session scan A 6966c2408200
pr-reviewer is an agent published in the GitHub repository mumerfarooq-con/asdlc-tools (2 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 1,034 once invoked, about $0.0004 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
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.
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.
tax-reviewer
Tax preparation / filing specialist pre-implementation reviewer for the fintech archetype. Outputs threat model TM-tax-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.