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 skills/pdurlej/jan-subagent/bmad-code-reviewnpx skills add pdurlej/jan-subagent --skill bmad-code-reviewgit clone --depth 1 https://github.com/pdurlej/jan-subagentWrote 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/skills/pdurlej/jan-subagent/bmad-code-review)<a href="https://agentmods.dev/skills/pdurlej/jan-subagent/bmad-code-review"><img src="https://agentmods.dev/badge/skills/pdurlej/jan-subagent/bmad-code-review.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.00050 | $0.00066 |
| Opus 5 | $0.00025 | $0.00033 |
| Sonnet 5 | $0.00010 | $0.00013 |
| Haiku 4.5 | $0.00005 | $0.00007 |
Grade A, and why
bmad-code-review 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 5d 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.
This is a copy
100% identical to bmad-code-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Follow the instructions in ./workflow.md.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 7 lines · 50 tokens per session scan A baca10e02574
bmad-code-review is a skill published in the GitHub repository pdurlej/jan-subagent (0 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 66 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bmad-code-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
nemoclaw-maintainer-refactor-docs
Plan and execute maintainer-owned refactors of oversized NemoClaw Fern documentation sections into focused one-topic pages with concise prose, journey-based nested navigation, non-clickable group nodes, canonical troubleshooting and reference ownership, deduplicated content, variant-aware route-style links, and…
nemoclaw-maintainer-validate-launchable
Validate the user-facing staging Brev Launchable deployment, NemoClaw image and runtime identity, onboarding, CLI behavior, and inference. Use when a maintainer asks to test the staging Launchable in the Brev web interface, provides a deployed Brev environment URL, hands a Launchable instance to Codex, or needs…
nemoclaw-contributor-create-pr
Create a GitHub pull request with the NemoClaw template. Then, monitor CI and automated reviews. Use this skill when the user asks to create, open, push, or submit a PR for review. Trigger keywords - create PR, pull request, new PR, submit for review, open PR, push for review.
nemoclaw-maintainer-pr-comparator
Compare open PRs that address the same issue and recommend one to merge. Apply eligibility, correctness, quality, and tie-break checks. Report the score and evidence. Use when an issue has two or more open PRs.
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
nemoclaw-contributor-plan-issue
Plan, refine, scope, or divide a NemoClaw GitHub issue into independently valuable capability slices before implementation. Use when a user asks to plan an issue, refine its scope, define acceptance evidence, break it down, split it, or identify the first capability slice. Ask which lifecycle stage they want when a…