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-generate-tasksgit 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-generate-tasks)<a href="https://agentmods.dev/skills/e0ipso/strikethroo/st-generate-tasks"><img src="https://agentmods.dev/badge/skills/e0ipso/strikethroo/st-generate-tasks/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/skills/e0ipso/strikethroo/st-generate-tasks"><img src="https://agentmods.dev/badge/skills/e0ipso/strikethroo/st-generate-tasks.svg" alt="Reviewed on agentmods" width="80" 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 23 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.00077 | $0.02187 |
| Opus 5 | $0.00039 | $0.01094 |
| Sonnet 5 | $0.00015 | $0.00437 |
| Haiku 4.5 | $0.00008 | $0.00219 |
Grade A, and why
st-generate-tasks 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
st-generate-tasks
Inputs
The user supplies the numeric plan ID conversationally.
Operating Procedure
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. Resolve the plan
Run scripts/validate-plan-blueprint.cjs <plan-id> planFile for the plan
file's absolute path. Another field name prints that field instead.
If the script exits non-zero, stop and ask the user to confirm the plan ID. Do not guess a different ID.
3. Load project context
Read these files, in order:
<root>/config/STRIKETHROO.md— project and directory conventions.- The plan body at the path returned by step 2 — the contract for what tasks must exist.
<root>/config/templates/TASK_TEMPLATE.md— the schema every task file must match.<root>/config/shared/anti-rationalization.md— apply in step 4.
4. Analyze and decompose the plan
Read the entire plan. Identify all concrete deliverables explicitly stated. Decompose each deliverable into atomic tasks only when genuinely needed.
Task minimization (mandatory):
- Create only the minimum number of tasks necessary. Target a 20–30% reduction from comprehensive lists by questioning the necessity of each candidate.
- Every task corresponds to an explicit requirement, never a nice-to-have, a "best practice", or future extensibility the plan does not mention.
- Each task has a unique, non-overlapping purpose.
- Keep error handling inside the task that owns the behavior it guards.
What ships with it
6 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 · -64 lines 2daa478d5f5d
- 3d ago Changed · -67 lines a6c12afe331b
- 9d ago First seen · 350 lines · 77 tokens per session scan A 25bb25bd101c
st-generate-tasks is a skill published in the GitHub repository e0ipso/strikethroo (50 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 2,187 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.