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 tomzx/agents --skill kill-initiativegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/kill-initiative)<a href="https://agentmods.dev/skills/tomzx/agents/kill-initiative"><img src="https://agentmods.dev/badge/skills/tomzx/agents/kill-initiative/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/tomzx/agents/kill-initiative"><img src="https://agentmods.dev/badge/skills/tomzx/agents/kill-initiative.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00578 |
| Opus 5 | $0.00016 | $0.00289 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
kill-initiative 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 6d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kill Initiative
Killing an initiative is hard and rarely encoded, so it gets its own skill. It converts a kill gate verdict (or a manual decision to stop) into a durable record, frees the capacity the initiative was consuming, and tells stakeholders.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - The initiative to stop (
$1asINIT-N, or resolve from.pdlc/state.yml).
Steps
- Locate the initiative directory under
.pdlc/initiatives/. - Record the kill via
make-decision(general decision) if no gate decision already recorded it. The decision body states the rationale: the strongest evidence that killed it (negative experiment, no real problem, cost > value, guardrail breach). - Update the initiative's
progress.md: setcurrent_phase: killed, recordkilled_atdate, and write a one-line rationale. - Reallocate capacity: update
.pdlc/context/roadmap.mdto remove or downgrade the initiative from its Now/Next/Later slot, freeing the slot for the next priority. - Capture a learning via
run-retrospectiveso the kill produces organizational knowledge, not just a silent deletion. What did we believe that turned out false? - Notify stakeholders: produce a brief via
brief-stakeholderssummarizing the decision, the rationale, and the capacity freed. Do not send anything without explicit user confirmation (commit/push/PR gate). - If the initiative had already shipped something, consider whether
sunset-productis also needed for the shipped artifact.
Output Format
## Initiative killed: INIT-N — <title>
Rationale: <one paragraph>
Evidence: <what we learned>
Capacity freed: <roadmap slot / person-weeks>
Stakeholder brief: <drafted, pending send>
Learning: <captured in .pdlc/learnings/>
Outcome
If $OUTCOME_YAML is set, emit verdict: killed.
Next Step
Run prioritize to refill the freed roadmap slot, or run-retrospective if not already done.
Completion Checklist
- A decision record exists recording the kill rationale
-
progress.mdmarkedkilledwith date and rationale - Roadmap capacity reallocated
- A learning captured so the kill compounds knowledge
- Stakeholder brief drafted (sending requires explicit confirmation)
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.
- 6d ago First seen · 53 lines · 33 tokens per session scan A e68644383a1d
kill-initiative is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 578 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.