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/jeremydev87/codingbuddy/plan-featuregit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWhat 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.00224 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
plan-feature 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 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.
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 Feature Command
Description
Analyze requirements and create structured implementation plan following .ai-rules standards.
Command
# Read context
READ packages/rules/.ai-rules/rules/core.md
READ packages/rules/.ai-rules/rules/project.md
READ packages/rules/.ai-rules/rules/augmented-coding.md
# Analyze project state
RUN git status
RUN git log --oneline -10
# Create plan
PLAN implementation for: $1
- Follow TDD cycle for core logic
- Use Test-After for UI components
- Maintain 90%+ test coverage
- Apply SOLID principles
- Generate todo list with priorities
- Include risk assessment
# Output in Korean
RESPOND in Korean (한국어)
Usage
# In OpenCode CLI
/plan-feature "사용자 등록 기능"
Expected Output
- Structured PLAN mode response
- Todo list creation using todo_write tool
- TDD vs Test-After strategy decision
- File structure planning
- Quality checklist
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 · 41 lines · 0 tokens per session scan A ecbb0901ee97
plan-feature is a command published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 224 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
extract
Analyze conversation history and extract reusable skills, commands, or agents.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
raw-export
Export raw conversation data directly from JSONL session files.
stats
Show statistics for saved conversation files.
update-plugins
Batch update all installed Claude Code plugins to latest versions.
setup
Initialize or update chat-saver configuration for the current project.