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 e0ipso/strikethroo --skill st-create-plangit clone --depth 1 https://github.com/e0ipso/strikethrooWrote 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/e0ipso/strikethroo/st-create-plan)<a href="https://agentmods.dev/skills/e0ipso/strikethroo/st-create-plan"><img src="https://agentmods.dev/badge/skills/e0ipso/strikethroo/st-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.00085 | $0.01002 |
| Opus 5 | $0.00043 | $0.00501 |
| Sonnet 5 | $0.00017 | $0.00200 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
st-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 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
st-create-plan
Drive the end-to-end creation of a new Strikethroo plan for the user's repository.
Inputs
The user's request supplies the work order.
Operating Procedure
1. Locate the strikethroo root
Run scripts/find-strikethroo-root.cjs from the user's working directory.
If the script exits non-zero, the working directory is not inside an
initialized strikethroo workspace. Stop and ask the user to run the project
initializer (e.g. npx strikethroo init) before continuing. Do
not attempt to create a plan outside of a valid root.
For every subsequent step, treat the path printed by this script as <root>.
2. Load project context
Read <root>/config/STRIKETHROO.md for the directory structure conventions
this project uses. Read <root>/config/hooks/PRE_PLAN.md and execute the
instructions it contains before proceeding. Read
<root>/config/templates/PLAN_TEMPLATE.md so the plan you emit conforms
to its structure.
Also read <root>/config/shared/clarification-gate.md and
<root>/config/shared/anti-rationalization.md. The steps below require you to
apply them.
3. Analyze the work order
Identify:
- Objective and end goal.
- Scope and explicit boundaries.
- Success criteria.
- Dependencies, prerequisites, blockers.
- Technical requirements and constraints.
4. Clarification loop
If any critical context is missing, ask the user targeted questions. Keep looping until you have no further questions. Explicitly confirm whether backwards compatibility is required. Never invent answers; never paper over a missing answer.
If the user declines to clarify a blocking question, stop and report the plan as needing clarification. Do not produce a partial plan.
Follow the clarification cadence in <root>/config/shared/clarification-gate.md.
Apply <root>/config/shared/anti-rationalization.md to this rationalization table:
| You catch yourself thinking… | The binding rule |
|---|---|
| "I can reasonably assume the answer." | An assumption is not an answer. Ask the question; never invent answers. |
| "Asking again is annoying." | A question the user can decline is recoverable; a silent wrong assumption is not. Ask. |
| "The user implied it, so it's settled." | An implication is not a confirmation. Surface it as a question and get an explicit answer. |
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.
- yesterday Changed · -13 lines bd82562a4c56
- 7d ago First seen · 136 lines · 85 tokens per session scan A cfe8b8a721f7
st-create-plan is a skill published in the GitHub repository e0ipso/strikethroo (48 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 1,002 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
hatch3r-board-groom
Ongoing backlog refinement for existing board items. Re-prioritize, reclassify, re-scope, archive stale items, decompose oversized issues, merge duplicates, refresh dependencies, and remediate board health findings.
hatch3r-board-init
Initializes a project board (GitHub Projects V2, Azure Boards, or GitLab Issue Boards) with hatch3r's label taxonomy, status fields, and board structure. Platform detected from hatch.json.
hatch3r-board-shared
Shared context and procedures for all board commands. Provides platform-agnostic board config, label taxonomy, branch conventions, sync enforcement, and tooling directives. Platform-specific details are in commands/board/shared-{platform}.md.
hatch3r-board-refresh
Regenerates the living board overview dashboard from current board state. Scans all open issues, computes health metrics, and updates the meta:board-overview issue.
hatch3r-cleanup
Repo-state cleanup pass — inventories accumulated hatch3r working state (plan files, workspace dirs, review telemetry, findings ledgers, learnings, handoffs, board staleness), asks once with per-category counts and estimated reclaim, dispatches each owned surface to its owning skill or CLI path, and prunes only the…
hatch3r-feedback
Captures user feedback on an agent recommendation or workflow outcome, classify it, sanitize it, and route it to the right destination — a local feedback record, a GitHub issue from the agent-recommendation-feedback template, or a learning. Use after an agent gives advice the user wants to rate, correct, or escalate.