Borrowing it
Nothing to install: this file belongs to WolframResearch/AgentTools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WolframResearch/AgentTools/main/.claude/skills/spec-to-todo/SKILL.mdgit clone --depth 1 https://github.com/WolframResearch/AgentToolsWrote 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/wolframresearch/agenttools/spec-to-todo)<a href="https://agentmods.dev/skills/wolframresearch/agenttools/spec-to-todo"><img src="https://agentmods.dev/badge/skills/wolframresearch/agenttools/spec-to-todo/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/wolframresearch/agenttools/spec-to-todo"><img src="https://agentmods.dev/badge/skills/wolframresearch/agenttools/spec-to-todo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 Rogue Agent · line 56 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 58 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 59 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00122 | $0.01111 |
| Opus 5.5 | $0.00049 | $0.00444 |
| Sonnet 5.5 | $0.00024 | $0.00222 |
| Haiku 4.5 | $0.00012 | $0.00111 |
Grade A, and why
spec-to-todo 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 1mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate TODO from Specification
Read a design specification and produce a TODO task list that captures everything needed to fully implement it, organized into logical work units.
Spec to process: $ARGUMENTS
If no specific spec is given, ask the user which spec in Specs/ they'd like to turn into a task list.
Process
1. Read the Spec
Read the full spec file from Specs/. Identify every deliverable it describes:
- Source files to create or modify
- Build scripts or tooling
- Generated artifacts (scripts, config files, packages)
- Hand-authored content (documentation, reference files, skill definitions)
- Tests and evals
- Directory structures that must exist
2. Explore Current State
Launch parallel Explore agents to understand what already exists. Focus on:
- What's implemented: Files that exist and have real content matching the spec.
- What's partial: Files that exist but are stubs/placeholders (e.g., contain only "TODO").
- What's missing: Files or directories the spec requires that don't exist at all.
- Discrepancies: Differences between the spec and reality (e.g., a manifest missing an entry, wrong directory structure, mismatched names).
Key areas to check:
- The directories and files the spec references directly
Scripts/for any build scripts mentionedKernel/for source code the spec depends on (tool definitions, parameters, etc.)Tests/for any existing test coverageNotes/for implementation hints or reference codedocs/for related developer documentation
3. Gap Analysis
Compare spec requirements against exploration results. For each deliverable, classify it:
- Done: Fully implemented, matches spec. Don't create a task for it.
- Partial: Exists but incomplete. Create a task describing what remains.
- Missing: Doesn't exist. Create a task for the full implementation.
- Discrepancy: Exists but doesn't match spec. Create a task to fix it.
4. Organize into Tasks
Group related work into logical units, where each task represents roughly one coding session. Guidelines:
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.
- 1mo ago First seen · 113 lines · 122 tokens per session scan A 77c748c1d28f
spec-to-todo is a skill published in the GitHub repository WolframResearch/AgentTools (96 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 1,111 once invoked, about $0.0005 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…