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-full-workflowgit 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-full-workflow)<a href="https://agentmods.dev/skills/e0ipso/strikethroo/st-full-workflow"><img src="https://agentmods.dev/badge/skills/e0ipso/strikethroo/st-full-workflow.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 49 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00090 | $0.04821 |
| Opus 5 | $0.00045 | $0.02410 |
| Sonnet 5 | $0.00018 | $0.00964 |
| Haiku 4.5 | $0.00009 | $0.00482 |
Grade A, and why
st-full-workflow 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 today.
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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
st-full-workflow
Critical Rule
Execute all three steps sequentially without waiting for user input between them.
Inputs
The user supplies the work order conversationally.
Operating Procedure
Step 1: Plan Creation
1. Locate the strikethroo root
Run scripts/find-strikethroo-root.cjs from the user's working directory. If
it exits non-zero, stop and ask the user to run npx strikethroo init.
Treat the path it prints as <root> for every subsequent step.
Delegated execution workers skip this step and do not emit update notices.
Run scripts/check-for-updates.cjs "<root>" as a separate command using this
skill's script path. Keep the user's working directory. Read the one JSON line
on stdout. When notice is present, retain its exact text for the final
user-facing response. Never pause for permission and never run an update.
2. Load project context
Read <root>/config/STRIKETHROO.md for this project's directory conventions.
Read <root>/config/hooks/PRE_PLAN.md and execute its instructions before
proceeding. Read <root>/config/templates/PLAN_TEMPLATE.md; the plan must
conform to it.
Also read <root>/config/shared/anti-rationalization.md.
3. Analyze the work order
Identify:
- Objective.
- 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.
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
11 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.
- references/complexity-rubric.md 833 B
- scripts/capture-base-commit.cjs 11 KB runs code
- scripts/check-for-updates.cjs 81 KB runs code
- scripts/check-phase-readiness.cjs 16 KB runs code
- scripts/create-feature-branch.cjs 13 KB runs code
- scripts/dispatch-task-execution.cjs 246 KB runs code
- scripts/find-strikethroo-root.cjs 4.3 KB runs code
- scripts/get-next-plan-id.cjs 6.9 KB runs code
- scripts/get-next-task-id.cjs 10 KB runs code
- scripts/route-task-execution.cjs 105 KB runs code
- scripts/validate-plan-blueprint.cjs 14 KB runs code
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.
- today Changed · -131 lines 5492d7f2f864
- 2d ago Changed · -66 lines 5f692f0f5063
- 4d ago Changed · -16 lines 933e60100b1c
- 8d ago First seen · 684 lines · 90 tokens per session scan A ca70d5f483db
st-full-workflow is a skill published in the GitHub repository e0ipso/strikethroo (49 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 4,821 once invoked, about $0.0005 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
business-requirements
Read and hand-edit the app's business requirements — the checklist the harness verifies the built app against. MUST be loaded whenever the user asks to add, change, remove, reword, re-prioritise, or reclassify a business requirement (e.g. "add a requirement that…", "that rule is wrong, fix it", "drop the requirement…
first-run-open
Owns the opening move of first-run when the user has NOT handed you a substantive prompt (cold start), and sets the voice-vs-text opening posture for any open. Shows a provisional dream and a guess about who the user is, then learns from their correction (show-to-learn) and re-aims. Hands back to the first-run spine…
disqualification
The honest exit. Loads when qualification signals sustained-low or a realism failure (the ask is genuinely outside QB's wheelhouse). Acknowledges the mismatch plainly, suggests a realistic alternative, preserves dignity, and does not chase. A legitimate designed outcome, not a framework failure.
qualification
Reads qualification signals from the user's input and passive context, sets the archetype and effort mode, and decides whether to proceed up the convince ladder or route to the disqualification skill. Runs alongside the first-run spine from the first substantive message onward. Falls back to "proceed at normal effort"…
build-recovery
Owns the build wait and build failure. Narrates the generation honestly while it runs, and when it errors, names the failure plainly with a real recovery path instead of a generic "oops". Loads when generation is long or returns an error. The single highest-risk moment for the "it's actually building" belief.
chat-formatting-widgets
Governs the custom markdown widgets rendered in the QuantumByte chat interface. This includes the inline highlight-mark span (use on every question the user must answer). You must check this skill on every reply to format highlights.