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/e0ipso/strikethroo/st-execute-tasknpx skills add e0ipso/strikethroo --skill st-execute-taskgit 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-execute-task)<a href="https://agentmods.dev/skills/e0ipso/strikethroo/st-execute-task"><img src="https://agentmods.dev/badge/skills/e0ipso/strikethroo/st-execute-task.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.00072 | $0.02144 |
| Opus 5 | $0.00036 | $0.01072 |
| Sonnet 5 | $0.00014 | $0.00429 |
| Haiku 4.5 | $0.00007 | $0.00214 |
Grade A, and why
st-execute-task 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
st-execute-task
Drive the execution of a single task within an existing Strikethroo plan.
The skill is assistant-agnostic and self-contained: every script it invokes
lives under this skill's scripts/ directory and is referenced by relative
path.
Critical Rules
- Never skip dependency validation — task execution requires all dependencies to be completed.
- Validate task status — never execute tasks that are already completed, in-progress, or needs-clarification.
- Maintain status integrity — update task status throughout the execution lifecycle.
- Document execution — record all outcomes and issues encountered.
- Provide structured output — always emit the structured result block for orchestrator parsing.
Inputs
The user supplies the numeric plan ID and task ID conversationally. Treat them as the only authoritative source of intent. Do not invent answers to clarifying questions — prompt the user instead.
Failure Modes
- No strikethroo root found. Stop and instruct the user to initialize the project. Do not execute the task.
- Plan ID does not resolve. Stop and surface the script's stderr to the user. Do not guess a different ID.
- Task file not found. Stop and list available tasks in the plan to help the user identify the correct task ID.
- Task status blocks execution. If the task is
completed,in-progress, orneeds-clarification, halt and provide guidance on resolving the blocker. - Dependency validation failure. If
scripts/check-task-dependencies.cjsexits 1, stop and report unresolved dependencies. Do not proceed until they are satisfied. - Execution or hook failure. If
PRE_TASK_EXECUTION.md,PRE_TASK_ASSIGNMENT.md, orPOST_ERROR_DETECTION.mdfails, or the implementing agent encounters an unrecoverable error, set the task status tofailed, document the error in Noteworthy Events, and emit the structured result withExit Code: 1.
Operating Procedure
1. Locate the strikethroo root
What ships with it
4 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.
- 4d ago First seen · 229 lines · 72 tokens per session scan A 1be517cd467b
st-execute-task is a skill published in the GitHub repository e0ipso/strikethroo (48 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 2,144 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
neuron-tool-creator
Create custom tools and toolkits for Neuron AI agents. Use this skill whenever the user mentions tools, functions, capabilities, agent actions, building tools, extending agent functionality, or wants to add custom capabilities to Neuron agents. Also trigger for tasks involving tool properties, tool execution…
maestro-extension
Help developers create and implement extensions for the Maestro CLI application. Use this skill whenever the user mentions creating a Maestro extension, adding custom tools or commands, building UI components for Maestro, registering memory files or event handlers, packaging a Composer package with Maestro extensions…
neuron-workflow-architect
Build custom Neuron AI workflows with nodes, events, middleware, and human-in-the-loop patterns. Use this skill whenever the user mentions workflows, orchestration, event-driven systems, custom agents, complex multi-step processes, human-in-the-loop patterns, or wants to build a custom agentic system from scratch.…
neuron-agent-builder
Create and configure Neuron AI agents with providers, tools, instructions, and memory. Use this skill whenever the user mentions building agents, creating AI assistants, setting up LLM-powered chat bots, configuring chat agents, or wants to create an agent that can talk, use tools, or handle conversations. Also…
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…