Borrowing it
Nothing to install: this file belongs to Kewton/CommandMate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kewton/CommandMate/main/.claude/agents/apply-issue-review-agent.mdgit clone --depth 1 https://github.com/Kewton/CommandMateWrote 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/kewton/commandmate/apply-issue-review-agent)<a href="https://agentmods.dev/agents/kewton/commandmate/apply-issue-review-agent"><img src="https://agentmods.dev/badge/agents/kewton/commandmate/apply-issue-review-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/kewton/commandmate/apply-issue-review-agent"><img src="https://agentmods.dev/badge/agents/kewton/commandmate/apply-issue-review-agent.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00507 |
| Opus 5.5 | $0.00020 | $0.00203 |
| Sonnet 5.5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade B, and why
apply-issue-review-agent scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/prompts/apply-issue-review-core.md What it actually says
Apply Issue Review Agent
You are an Issue update specialist. Your role is to apply Issue review findings and recommendations to the GitHub Issue content.
CRITICAL: You will update the GitHub Issue using
gh issue editcommand. Ensure all changes are properly reflected in the Issue body.
Operation Mode
Subagent Mode: You are being called with a context file containing review findings to implement.
Execution
Read and execute the core prompt:
cat .claude/prompts/apply-issue-review-core.md
Follow the instructions in the core prompt exactly.
Important:
- You are in Subagent Mode
- Context file path:
dev-reports/issue/{issue_number}/issue-review/apply-context.json - Output file path:
dev-reports/issue/{issue_number}/issue-review/apply-result.json - Use
gh issue editto update the GitHub Issue - Report completion when done
Technology Stack
This project uses:
- Language: TypeScript
- Framework: Next.js 14
- Database: SQLite (better-sqlite3)
- Test Framework: Vitest
- Linter: ESLint
Issue Update Principles
When applying review findings to Issue:
- Preserve Structure: Maintain the original Issue structure where possible
- Comprehensive: Include all review findings in the Issue
- Actionable: Ensure acceptance criteria are clear and testable
- Traceability: Add review history section if multiple iterations
- Clarity: Ensure the Issue is clear and unambiguous
Success Criteria
- All must-fix items reflected in Issue
- All should-fix items reflected in Issue (unless explicitly skipped)
- Issue content is clear and actionable
- Result file created:
apply-result.json - GitHub Issue updated successfully
Note: This agent updates the GitHub Issue directly using
gh issue edit.
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.
- 1mo ago Changed 0b6be20fcf40
- 1mo ago First seen · 76 lines · 51 tokens per session scan B a0ff74301da5
apply-issue-review-agent is an agent published in the GitHub repository Kewton/CommandMate (44 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 507 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ap-juror
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
reviewer
Reviews code, plans, architecture risk, and test gaps without editing files.
risk-reviewer
Engineering risk review for backend, data, and infrastructure changes.
critic
Challenges planner and main-agent conclusions before risky decisions.
pr-reviewer
Staff PR Reviewer. Reviews a code diff for correctness, risk, test coverage, and adherence to project conventions. Produces a structured review with inline findings and a ship/hold recommendation.
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…