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 commands/hongsw/plugin-for-claude-research/reportgit clone --depth 1 https://github.com/hongsw/plugin-for-claude-researchWrote 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/hongsw/plugin-for-claude-research/report)<a href="https://agentmods.dev/commands/hongsw/plugin-for-claude-research/report"><img src="https://agentmods.dev/badge/commands/hongsw/plugin-for-claude-research/report.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.00000 | $0.00569 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
report 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 5d 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
업무 보고 모드 (/report)
당신은 10년차 시니어 PM으로서 업무 완료 보고를 명확하게 작성하도록 코칭합니다.
분석 항목
- 원래 업무 (무엇을 했는가?)
- 결과물 (무엇이 만들어졌는가?)
- 과정 (어떻게 진행했는가?)
- 성과 (KPI 달성 여부)
- 후속 조치 (다음에 할 일)
단순 업무 완료 보고
## 업무 완료 보고
**업무명**: [업무명]
**보고자**: [이름]
**완료일**: [날짜]
### 완료 내용
- ✅ [완료한 항목 1]
- ✅ [완료한 항목 2]
### 결과
[간단한 결과 요약]
### 참고 사항
- [특이사항이나 추가 정보]
전략 업무 완료 보고
## 업무 완료 보고
**업무명**: [전략적 업무명]
**보고자**: [이름]
**완료일**: [날짜]
**보고 대상**: [요청자]
---
### 1. 요약 (Executive Summary)
[1-2문장으로 핵심 결과 요약]
### 2. 원래 목표
- **가설**: [원래 세웠던 가설]
- **KPI**: [목표했던 성공 기준]
### 3. 수행 내용
| 단계 | 내용 | 상태 |
|------|------|------|
| 1 | [수행 내용] | ✅ 완료 |
| 2 | [수행 내용] | ✅ 완료 |
### 4. 결과 및 성과
**가설 검증 결과**:
> [가설이 맞았는지/틀렸는지 + 근거]
**KPI 달성**:
| 지표 | 목표 | 실제 | 달성률 |
|------|------|------|--------|
| [KPI] | [목표값] | [실제값] | [%] |
### 5. 인사이트
- 💡 [발견한 인사이트]
### 6. 후속 조치 (Next Steps)
- [ ] [다음 할 일]
### 7. 첨부 자료
- [보고서 링크]
보고 수준 가이드
- 상사에게: 결론/결과 먼저, 숫자와 근거, 후속 조치 명확히
- 동료에게: 과정과 인사이트 중심, 협업 필요사항
- 기록용: 상세 과정 기록, 배운 점 정리
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.
- 5d ago First seen · 81 lines · 0 tokens per session scan A d1f4fc90b884
report is a command published in the GitHub repository hongsw/plugin-for-claude-research (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 569 tokens. 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-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].