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/kewton/commandmate/apply-issue-review-agentgit clone --depth 1 https://github.com/Kewton/CommandMateWhat 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.00051 | $0.00507 |
| Opus 5 | $0.00026 | $0.00253 |
| Sonnet 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 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.
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.
- 3d 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 (39 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 507 once invoked, about $0.0003 per session on Opus 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
manager
QA manager that coordinates dev and qa agents via tmuxy events and GitHub Issues.
qa
QA agent that runs rotating test styles and creates/updates GitHub Issues for findings.
dev
Dev agent that implements bug fixes assigned by the manager, reports progress via GitHub issue comments.
e2e-headless
Tools/dev-sshd/harness.sh runs a user-mode sshd on 127.0.0.1:2222 (own keys under Tools/dev-sshd/state/, never touches /.ssh).
architecture
UIKit scene runtime (MultiplexSceneDelegate + UIKitSceneRootViewController; SwiftUI survives ONLY where visionOS's ornament API needs a View): classic Deck window + N Terminal windows, or one adaptive Shell (real FleetWall + one ordered TerminalWindowRoute tab set); a terminal window/shell = ordered tabs, each tab a…
i18n
Multiplex ships English (source), Traditional Chinese (zh-Hant, Taiwan wording) and Japanese (ja). Decisions below were settled 2026-08-18; do not re-litigate without new facts.