Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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.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.1 | $0.00122 | $0.01111 |
| Opus 5 | $0.00061 | $0.00556 |
| Sonnet 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 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 — 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.
- 6d 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 (85 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 1,111 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…