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 skills add mishahanin/heading-os --skill create-plangit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/create-plan)<a href="https://agentmods.dev/skills/mishahanin/heading-os/create-plan"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/create-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.1 | $0.00079 | $0.01389 |
| Opus 5 | $0.00039 | $0.00694 |
| Sonnet 5 | $0.00016 | $0.00278 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
create-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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-plan — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Create a detailed implementation plan for changes to this workspace. Plans are thorough documents that capture the full context, rationale, and step-by-step tasks needed to execute a change with complete alignment across the project.
Variables
request: $ARGUMENTS (describe what you want to plan — new command, new workflow, structural change, template update, etc.)
Instructions
- IMPORTANT: You are creating a PLAN, not implementing changes. Research thoroughly, think deeply, then output a comprehensive plan document.
- Use your reasoning capabilities to think hard about the request, workspace structure, and best approach.
- Research the workspace to understand existing patterns, conventions, and how this change fits.
- Create the plan in the
plans/directory with filename:YYYY-MM-DD-{descriptive-name}.md- Use today's date
- Replace
{descriptive-name}with a short, kebab-case name (e.g., "add-guest-research-command", "restructure-outputs", "create-outreach-workflow")
- Fill out every section of the Plan Format below. Replace all
<placeholders>with specific, actionable content. - Be thorough — this plan will be executed by
/implementand needs enough detail to execute without ambiguity. - Follow existing patterns. Study similar files in the workspace before proposing new structures.
Research Phase
Before writing the plan, investigate:
-
Read core reference files:
CLAUDE.md— workspace overviewcontext/— background context on the user and project
-
Explore relevant areas:
- If creating a skill: read existing skills in
.claude/skills/ - If modifying outputs: explore
outputs/structure and examples - If updating templates: check
reference/for existing patterns - If adding scripts: review
scripts/for conventions
- If creating a skill: read existing skills in
-
Understand connections:
- How does this change relate to existing workflows?
- What files reference or depend on areas being changed?
- Are there naming conventions to follow?
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 128 lines · 79 tokens per session scan A 101a6ed114cf
create-plan is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 79 tokens to every session and 1,389 once invoked, about $0.0004 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 skills, from other repositories
shogun-bloom-config
An interactive wizard that creates model-routing settings from your AI subscription choices. Model routing decides which available model handles each kind of task.
shogun-model-list
A reference table of AI command-line tools, their available models, subscription requirements, and maximum Bloom capability levels. Bloom's Taxonomy is a scale describing thinking tasks, from remembering information to creating new designs.
shogun-model-switch
A live-switching tool for changing which command-line AI agent, model, and reasoning mode is running. It updates settings, restarts the agent, and refreshes the displayed session information.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
shogun-readme-sync
A skill that compares an English README with its Japanese counterpart and brings them back into alignment. A README is the project document that explains what the software is and how to use it.
shogun-agent-status
A skill that shows whether the agents in a multi-agent Japanese feudal-themed team are working, waiting, missing, or assigned tasks. It combines terminal session status, task files, and unread messages.