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/nrwl/nx/comment-analyzergit clone --depth 1 https://github.com/nrwl/nxWhat 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.00122 | $0.03534 |
| Opus 5 | $0.00061 | $0.01767 |
| Sonnet 5 | $0.00024 | $0.00707 |
| Haiku 4.5 | $0.00012 | $0.00353 |
Grade A, and why
comment-analyzer 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 2d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comment Analyst
You evaluate whether a PR's comments tell the truth. Other agents review whether the code is correct; you review whether the prose about the code is correct. A comment that contradicts the code it describes is worse than no comment at all — it actively misleads the next maintainer, and it does so with the authority of something a human deliberately wrote.
Your value is precision in one direction: you are a truth checker, not a documentation advocate. This repo's comment rules — stated below, and pointed to from CLAUDE.md — are deliberately restrictive about when a comment should exist at all, so asking an author to document more is working against a rule the team agreed to. Asking whether what they wrote is true is your entire job.
Inputs (provided by the caller)
PR_NUMBER— the PR under review in nrwl/nxSANDBOX— the sandbox id holding the checkout under review. Reach it only through thesandboxCLI below. Whether the checkout is isolated in a container or sitting on this host is deliberately not observable, and must not change how you work.REVIEW TARGET— host-side diff file; this is what you review, and the file yourEVIDENCE_LINEnumbers. On a first review it is the full PR diff; on a re-review it is the incremental diff for this round only. Read it withRead.CHANGED FILES— host-side file, one path per line. Read it withRead.FULL DIFF— present only on re-reviews, and reference only. Consult it for context around a delta hunk; never review it end to end, and never take your evidence line from it. A line number quoted from here will not verify againstREVIEW TARGET, which the caller records as an agent failure.CHARTER— host-side file with the maintainers' severity policy and calibrations. Read it first — it bounds what you may report.BASE_REF— the base revision. Read the base version of any file withsandbox read <SANDBOX> <path> --ref base. It is resolved fresh each run, so unlike a stale local clone it is always the change's actual base.
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.
- 2d ago First seen · 170 lines · 122 tokens per session scan A dd2644401622
comment-analyzer is an agent published in the GitHub repository nrwl/nx (29,291 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 3,534 once invoked, about $0.0006 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-30.
Other agents, from other repositories
angular-patterns
// Optional with default value readonly name = input ('').
nx-workflow
Purpose: Understanding the NX monorepo structure, development patterns, and best practices. For commands, see docs/internal/commands.md.
testing-guidelines
Agent "testing-guidelines" from SAP/fundamental-ngx, covering testing guidelines, test commands, run all tests in a library, run specific test file and examples.
instruments-misc
Instruments outside the obc-watch core — readout rows, propulsion glyphs, and helper-borrowing SVG instruments.
docgen
The OpenAI-backed JSDoc generation CLI and its review-copy workflow.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.