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/Smirnov-Labs/claude-skillsWrote 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/smirnov-labs/claude-skills/plan)<a href="https://agentmods.dev/commands/smirnov-labs/claude-skills/plan"><img src="https://agentmods.dev/badge/commands/smirnov-labs/claude-skills/plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/smirnov-labs/claude-skills/plan"><img src="https://agentmods.dev/badge/commands/smirnov-labs/claude-skills/plan.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00338 |
| Opus 5 | $0.00004 | $0.00169 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
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 12d 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
Planning Mode
You are now entering Planning Mode. Follow this structured process:
Step 1: Review Memory Bank
Read all memory bank files in order:
.claude/memory-bank/memory-rules.md.claude/memory-bank/projectbrief.md.claude/memory-bank/productContext.md.claude/memory-bank/systemPatterns.md.claude/memory-bank/techContext.md.claude/memory-bank/activeContext.md.claude/memory-bank/progress.md
Step 2: Analyze Request
Deeply reflect upon the changes being asked and analyze existing code to map the full scope of changes needed.
Step 3: Ask Clarifying Questions
Before proposing a plan, ask 4-6 clarifying questions based on your findings. These questions should:
- Address ambiguities in requirements
- Clarify technical approach preferences
- Identify potential risks or concerns
- Understand constraints or priorities
Step 4: Draft Plan
Once questions are answered, create a comprehensive plan that includes:
- Overview of approach
- Detailed phases/steps
- Files to be modified/created
- Potential challenges
- Testing strategy
- Success criteria
Step 5: Get Approval
Present the plan clearly and ask for user approval before proceeding.
Step 6: Execute
Once approved:
- Use TodoWrite to track all steps
- Implement systematically
- After completing each phase, mention what was completed and what remains
- Update memory bank as you progress
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.
- 12d ago First seen · 47 lines · 8 tokens per session scan A 14b5cfd22e86
plan is a command published in the GitHub repository Smirnov-Labs/claude-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 338 once invoked, about $0.0000 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-31.
Other commands, from other repositories
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.