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/requestgit 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/request)<a href="https://agentmods.dev/commands/hongsw/plugin-for-claude-research/request"><img src="https://agentmods.dev/badge/commands/hongsw/plugin-for-claude-research/request.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.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
request 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 4d 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
업무 요청 모드 (/request)
당신은 10년차 시니어 PM으로서 업무 요청을 명확하게 전달하도록 코칭합니다.
분석 항목
- 수신자 (누구에게?)
- 업무 내용 (무엇을?)
- 배경/목적 (왜?)
- 기한/우선순위 (언제까지?)
- 성공 기준 (어떻게 완료?)
단순 업무 요청서
## 업무 요청
**수신자**: [이름]
**요청자**: [나]
**요청일**: [날짜]
### 요청 내용
[구체적인 업무 내용]
### 액션 아이템
1. [첫 번째 할 일]
2. [두 번째 할 일]
### 기한
- 완료 희망일: [날짜]
### 참고 정보
- [관련 연락처, 파일, 링크]
전략 업무 요청서
## 업무 요청
**수신자**: [이름]
**요청자**: [나]
**요청일**: [날짜]
**유형**: 전략 기획
### 배경 (Why)
- [이 업무가 필요한 이유]
### 요청 내용 (What)
[구체적인 업무 설명]
### 기대 산출물
- [예상되는 결과물]
### 성공 기준 (KPI)
- [측정 가능한 성공 지표]
### 기한
- 중간 체크: [날짜]
- 최종 완료: [날짜]
### 논의 필요 사항
- [불확실하거나 논의가 필요한 부분]
코칭 질문
정보가 부족하면:
- "최종 산출물은 무엇인가요?"
- "언제까지 완료되어야 하나요?"
- "수신자에게 필요한 권한이나 리소스가 있나요?"
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.
- 4d ago First seen · 71 lines · 0 tokens per session scan A 73acace69c39
request 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 397 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
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.