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/emcd/nb-mcp-server/reviewsgit clone --depth 1 https://github.com/emcd/nb-mcp-serverWhat 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.00000 | $0.01187 |
| Opus 5 | $0.00000 | $0.00593 |
| Sonnet 5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
reviews 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegated Review Flow
Use this flow when multiple team members can access the same repository through branches or linked worktrees.
Engineer Flow
- Implement the scoped change and run validation.
- Create a local/private review commit so the diff is hash-stable and hook-checked.
- Rebase the review branch onto the agreed
<local-integration-base>. - Send the commit hash, changed-file summary, validation results, and any blockers/design questions.
- The reviewer approves the commit or requests changes.
- Address reviewer feedback with fixup commits or first-class follow-up commits as described below.
- Autosquash targeted fixups before the final review packet, unless the integrator explicitly asks to inspect the unsquashed response stack first.
The agreed <local-integration-base> is a Git ref in the current repository, such as local master or a local lane integration branch. It is not a filesystem path and is not a remote-tracking ref. Do not use origin/master, another origin/* ref, a path like /path/to/repo/master, or a raw commit hash as the rebase base unless the coordinator explicitly names that exact ref or hash. When in doubt, ask for the local branch/ref name before rebasing. Confirm it with git branch --list <local-integration-base> or git rev-parse --verify <local-integration-base> before running git rebase.
Coordinator/Tech-Lead Flow
- Review the submitted commit and any included validation evidence.
- If targeted fixups remain, ask the author to autosquash them and resubmit the final review packet before merge, unless you explicitly want to inspect the unsquashed response stack first.
- Merge approved review branches with
--no-ffwhen preserving a delegated-work or lane boundary; this creates a clear integration point and avoids mutually rebasing branches into increasingly long histories. - Merge/push only after explicit human approval.
Prefer reviewing commits by hash. Use an explicit worktree path only for uncommitted diffs or commits in a different repository. Use patch artifacts only as a fallback when the reviewer cannot access the repository, branch, or worktree directly.
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 · 65 lines · 0 tokens per session scan A 2d55146dea62
reviews is an agent published in the GitHub repository emcd/nb-mcp-server (1 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,187 tokens. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.