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/jo-duchan/tapflow/work-plangit clone --depth 1 https://github.com/jo-duchan/tapflowWhat 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.00023 | $0.00290 |
| Opus 5 | $0.00012 | $0.00145 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
work-plan 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 today.
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
아래 토픽에 대한 Plan 문서를 작성한다: $ARGUMENTS
규칙
.work/YYYY-MM-DD-{topic}-plan.md파일을 새로 생성한다. (오늘 날짜 사용).work/CLAUDE.md의 frontmatter 형식과 파일 명명 규칙을 반드시 따른다.type: plan,status: draft로 시작한다.
문서 구조
---
created: YYYY-MM-DD
status: draft
type: plan
phase: (해당 시 기입, 없으면 생략)
topic: 한 줄 요약
---
## Goal
무엇을 왜 만드는가. 1~3문장.
## Requirements
- [ ] 요구사항 1
- [ ] 요구사항 2
## Out of Scope
이번 작업에서 다루지 않는 것.
## Test Cases
| # | 시나리오 | 입력 | 기대 결과 |
|---|----------|------|-----------|
| 1 | ... | ... | ... |
## Open Questions
결정이 필요한 사항. 작업 시작 전 해소해야 할 것.
문서 작성 후 파일 경로를 알려준다.
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.
- today Changed · +2 tokens per session 5b3a02def9a0
- 2d ago First seen · 45 lines · 21 tokens per session scan A e2ae1493df8e
work-plan is a command published in the GitHub repository jo-duchan/tapflow (543 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 5. 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
feature
Post a feature to the Features Board on production and write tweets.
commit
Smart commit that stages only conversation-relevant changes.
commit-all
Group all changes semantically and commit each group separately.
audit
Scan a codebase for existing observability instrumentation and identify gaps.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
platform-info
Detect project type (Android/iOS/KMP), list platforms, show platform info, and delegate to appropriate commands.