Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add juanmhidalgo/claude-plugins/plugin install code-reviewWrote 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/commands/juanmhidalgo/claude-plugins/dismiss)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/dismiss"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/dismiss.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.00034 | $0.00635 |
| Opus 5 | $0.00017 | $0.00318 |
| Sonnet 5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
dismiss 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Repository: !
git remote get-url origin - Current branch: !
git branch --show-current - PR Number: $ARGUMENTS
Instructions
Step 1: Get Comments to Dismiss
Check if there's a recent /code-review/triage output in this conversation with FALSE POSITIVES identified.
If not, fetch PR comments:
${CLAUDE_PLUGIN_ROOT}/scripts/pr-triage-comments.sh OWNER REPO PR_NUMBER
Step 2: For Each False Positive
Show the comment and ask for confirmation:
Comment by @copilot on `file.py:42`:
"Consider using dependency injection here..."
Dismiss with reason:
1. Already handled elsewhere
2. YAGNI - not needed
3. Misunderstands context
4. Style preference, not bug
5. Custom reason...
Step 3: Dismiss on GitHub
For each confirmed dismissal, run:
${CLAUDE_PLUGIN_ROOT}/scripts/pr-resolve-comment.sh OWNER REPO PR_NUMBER REF_ID dismiss "REASON"
This will:
- Add a reply with "Dismissed" + reason
- Resolve the thread on GitHub
Step 4: Report
Show summary:
## Dismissed Comments
✅ @copilot on file.py:42 - "YAGNI - not needed"
✅ @gemini on auth.py:15 - "Already handled in middleware"
✅ @copilot on utils.py:88 - "Style preference, not bug"
3 comments dismissed and resolved on PR #42
Dismissal Reasons Templates
| Reason | Template |
|---|---|
| YAGNI | "Not implementing - this feature isn't needed (YAGNI). The current implementation meets requirements." |
| Already handled | "Already handled in {location}. See {file}:{line} for the existing implementation." |
| Context | "This suggestion misunderstands the context. {explanation}" |
| Style | "This is a style preference, not a bug or security issue. Keeping current approach for consistency." |
| Breaking | "This change would break {what}. Current implementation is intentional." |
| Performance | "Verified no performance issue here. {evidence}" |
Important
- Be professional in dismissal messages
- Include enough context for future reference
- Don't dismiss valid concerns - only confirmed false positives
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 · 93 lines · 34 tokens per session scan A 2953662ca8b4
dismiss is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 12d ago), licensed MIT. It adds 34 tokens to every session and 635 once invoked, about $0.0002 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 commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.