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 skills/lacerbi/dotclaude/plannpx skills add lacerbi/dotclaude --skill plangit clone --depth 1 https://github.com/lacerbi/dotclaudeWrote 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/skills/lacerbi/dotclaude/plan)<a href="https://agentmods.dev/skills/lacerbi/dotclaude/plan"><img src="https://agentmods.dev/badge/skills/lacerbi/dotclaude/plan.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.00010 | $0.01703 |
| Opus 5 | $0.00005 | $0.00851 |
| Sonnet 5 | $0.00002 | $0.00341 |
| Haiku 4.5 | $0.00001 | $0.00170 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are entering PLANNING MODE. Explore and analyze before doing any work.
Phase 1: Task Understanding
State your understanding of the task: $ARGUMENTS
If unclear, use AskUserQuestion to clarify before proceeding.
Assess complexity to calibrate planning depth:
- Simple: Single-focus task, few components → lighter exploration, concise plan
- Moderate: Multiple components or unknowns → targeted exploration, structured plan
- Complex: Cross-cutting concerns, many dependencies → thorough exploration, detailed plan
Phase 2: Exploration
Explore the project to understand what exists and what the task involves. Scale exploration to task complexity.
For simple tasks: You may explore directly without subagents.
For moderate/complex tasks: Spawn Explore agents in parallel (Agent tool, subagent_type='Explore'), each focused on a relevant aspect:
- Structure Explorer: Project organization, key components, how things connect
- Prior Work Explorer: Existing similar work, patterns, or approaches to build on
- Context Explorer: Related materials, dependencies, constraints
- Domain Explorer: Subject matter, conventions, standards relevant to the task
- Docs Explorer: Documentation (READMEs, guides, API docs, comments) — what exists in or adjacent to the task area, what will need updating, and what doesn't exist yet but should
(For code-heavy tasks: Architecture, Feature, Dependency, Test explorers may be more appropriate)
Subagent selection: Opus for tasks requiring judgment. Sonnet for straightforward subtasks. Haiku only for trivial read-only tasks.
Instruct Explore agents to:
- Return hypotheses, not conclusions
- Provide full file paths for relevant files
- Identify locations, not deep analysis
- Be thorough but efficient - scouts, not implementers
Phase 3: Synthesis
After exploration:
- Read/verify key files and materials identified
- Confirm or refute hypotheses
- Build a mental model of the current state and what the task requires
- Identify existing documentation that must be updated, and whether any new document has a distinct durable purpose
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 · 187 lines · 10 tokens per session scan A cc10ec73b247
plan is a skill published in the GitHub repository lacerbi/dotclaude (2 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 1,703 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-31.
Other skills, from other repositories
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
deepstream-sop
Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…
cupynumeric-migration-readiness
Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment…