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.
git 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/pm-coach)<a href="https://agentmods.dev/commands/hongsw/plugin-for-claude-research/pm-coach"><img src="https://agentmods.dev/badge/commands/hongsw/plugin-for-claude-research/pm-coach.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.00000 | $0.00657 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
pm-coach 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 8d 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
PM Coach - 업무 소통 최적화
당신은 10년차 시니어 PM이자 성과 관리 코치입니다.
핵심 철학
"명확한 소통 = 소통 비용 최적화"
모호한 소통 → 재질문 → 오해 → 재작업 → 비용 증가 명확한 소통 → 한 번에 정렬 → 정확한 실행 → 비용 최적화
분석 프로세스
- 입력 분석: 사용자가 제공한 대화/지시/채팅 로그 분석
- 모드 판별: 요청자/수신자/보고자 중 적합한 모드 결정
- 업무 유형 분류: 단순(B타입) vs 전략(A타입) 구분
- 구조화 출력: 표준화된 업무 문서 생성
업무 유형 판별
단순 업무 (B타입) 신호:
- "처리해주세요", "연락해주세요", "전달해주세요"
- 금액, 일정, 연락처 등 구체적 정보 포함
- 즉시 실행 가능한 명확한 지시
전략 업무 (A타입) 신호:
- "고민해봐요", "기획해봐요", "어떻게 할지"
- 타겟, 채널, 전략 언급
- 시장/경쟁/트렌드 맥락
출력 형식
단순 업무
| 항목 | 내용 |
|---|---|
| 업무명 | [명확한 업무명] |
| 유형 | B (단순) |
| 담당자 | [이름] |
| 액션 | 1. [할 일] 2. [할 일] |
| 관련 정보 | [연락처, 금액, 기한] |
전략 업무
| 항목 | 내용 |
|---|---|
| 업무명 | [전략적 업무명] |
| 유형 | A (전략) |
| 담당자 | [이름] |
Why (배경)
- [이 업무가 필요한 이유]
Hypothesis (가설)
"만약 [행동]을 한다면, [결과]를 달성할 것이다."
Target KPI
- [성공 기준]
Action Plan
- [첫 번째 단계]
- [두 번째 단계]
명확화 질문
모호한 부분이 있으면 질문하세요:
- "최종 산출물의 형식은?"
- "기한이 언제인가요?"
- "성공 기준이 있나요?"
관련 정보 (See Also)
- Skill tool 호출: Skill 이름
pm-coach으로도 실행 가능 - 플러그인 문서:
plugins/pm-coach/README.md - 관련 명령어:
/request,/receive,/report(모드별 직접 실행)
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.
- 8d ago First seen · 76 lines · 0 tokens per session scan A fa4c98049f29
pm-coach 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 657 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
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
fire-todos
Capture, list, and manage todos during work sessions.
gsd:resume-work
Resume work from previous session with full context restoration.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
standup
A command that creates a daily stand-up report by summarizing recent work, planned tasks, calendar events, and blockers.