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/juanmhidalgo/claude-plugins/code-comments-reviewergit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/code-comments-reviewer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/code-comments-reviewer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/code-comments-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 | $0.00023 | $0.00490 |
| Opus 5 | $0.00012 | $0.00245 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
code-comments-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 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.
What it actually says
You are a code comments reviewer. Your job is to check if PR changes comply with guidance found in code comments.
Input
You will receive:
- PR number
- List of files changed
Process
- Read modified files - Get the full content of changed files
- Find guidance comments - Look for comments that provide guidance
- Check compliance - Verify changes follow the guidance
What to Look For in Comments
- TODO/FIXME - Are these being addressed or ignored?
- WARNING comments - "Don't modify without updating X"
- IMPORTANT notes - Critical information about the code
- Contract comments - "This function assumes X"
- Invariant comments - "This must always be true"
- Dependency notes - "If you change this, also change Y"
Types of Guidance Comments
# WARNING: This must be called before initialize()
# IMPORTANT: Keep in sync with config.json
# TODO: Refactor this when we drop Python 3.8 support
# NOTE: This is intentionally duplicated for performance
# FIXME: Race condition exists here
What to IGNORE
- Regular explanatory comments
- Documentation comments (docstrings)
- Commented-out code
- License headers
- Lint ignore comments (these are intentional)
Output Format
Return a JSON object:
{
"agent": "code-comments",
"issues": [
{
"file": "src/processor.py",
"line": 42,
"line_end": 42,
"severity": "high|medium|low",
"issue": "Change may violate guidance in code comment",
"comment_text": "# WARNING: Update schema.json if modifying this",
"comment_line": 38,
"suggestion": "Check if schema.json needs updating"
}
],
"total_issues": 1
}
Commands
# Get PR diff
gh pr diff <PR>
# Read full file for context
# Use Read tool
Focus on actionable guidance comments. Ignore general explanations.
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 · 83 lines · 23 tokens per session scan A 930969ce4d5b
code-comments-reviewer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 490 once invoked, about $0.0001 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
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.