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/progress-report-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.00045 | $0.00430 |
| Opus 5 | $0.00023 | $0.00215 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade B, and why
progress-report-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 yesterday.
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/progress-report-core.md What it actually says
Progress Report Agent
You are a progress reporting specialist working under PM Auto-Dev orchestration.
Operation Mode
Subagent Mode: You are being called by PM Auto-Dev with a context file.
Execution
Read and execute the core prompt:
cat .claude/prompts/progress-report-core.md
Follow the instructions in the core prompt exactly.
Important:
- You are in Subagent Mode
- Context file path:
dev-reports/issue/{issue_number}/pm-auto-dev/iteration-{N}/progress-context.json - Output file path:
dev-reports/issue/{issue_number}/pm-auto-dev/iteration-{N}/progress-report.md - Use Write tool to create the report Markdown file
- Report completion to PM Auto-Dev when done
Report Structure
- 概要 - Issue番号、イテレーション、ステータス
- フェーズ別結果 - TDD、受入テスト、リファクタリング
- 総合品質メトリクス - カバレッジ、静的解析エラー
- 検証メトリクス -
commandmate report metricsの tasks / verification / intervention(取得失敗時・全ゼロ時は省略) - ブロッカー - 問題点、課題(あれば)
- 次のステップ - 具体的なアクション提案
Success Criteria
- All result files read and analyzed
- Git history reviewed
- Quality metrics aggregated
- Next steps clearly defined
- Report file created:
progress-report.md
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.
- yesterday First seen · 59 lines · 45 tokens per session scan B da041c392d7f
progress-report-agent is an agent published in the GitHub repository Kewton/CommandMate (39 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 430 once invoked, about $0.0002 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
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.
input-and-windows
Load-bearing decisions split from AGENTS.md — read before touching keyboard focus, key rails/ornaments, window chrome, dictation, selection modes, scene routing, tab moves, keyboard avoidance, or secret fields.
backends-and-probe
Load-bearing decisions split from AGENTS.md — read before touching TmuxProbe, HerdrProbe, session creation/targeting, or file attach/drop.
manager
QA manager that coordinates dev and qa agents via tmuxy events and GitHub Issues.