Borrowing it
Nothing to install: this file belongs to causify-ai/helpers. 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/causify-ai/helpers/master/.claude/skills/auto_task.create_specs_from_todos/SKILL.mdgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/auto_task.create_specs_from_todos)<a href="https://agentmods.dev/skills/causify-ai/helpers/auto_task.create_specs_from_todos"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/auto_task.create_specs_from_todos/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/causify-ai/helpers/auto_task.create_specs_from_todos"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/auto_task.create_specs_from_todos.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.00010 | $0.00589 |
| Opus 5.5 | $0.00004 | $0.00236 |
| Sonnet 5.5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
auto_task.create_specs_from_todos 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 29d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Given a list of TODOs provided by the user in the form of a cfile create a plan to fix them
Workflow
Understand Each TODO
- Each TODO is in the form
<FILE>:<LINE_NUM>:<TODO description>- E.g.,
./helpers/hmarkdown_coloring.py:235:def colorize_bullet_points_in_slide(...
- E.g.,
- Read each TODO and understand the problem
- If it's a bug:
- Make sure to understand the root cause
- Run experiments to verify that you understood the issue and its root cause
- Devise a plan to fix the problem
- Devise a plan to verify that the problem is fixed
Write the Fix Plan
- Create a plan
tasks.mdfor fixing the tests using the template below.claude/templates/auto_task.template.md - Fill in the template's
* Repo:checklist per.claude/skills/auto_task.rules.mdsection "Multi-Repo Issues, Branches, and PRs" (how to tell which repo a<FILE>belongs to, and how to handle TODOs spanning more than one repo) - Write the comments as bullet points according to
.claude/skills/markdown.rules.mdand.claude/skills/text.rules.mdwith minimal text - Do not make any change to the code, but only propose the fixes
Follow the Conventions
- Follow
.claude/skills/auto_task.rules.mdsection "Follow the Coding and Testing Rules"- Refer to skills in
.claude/skills/coding.*/SKILL.mdand.claude/skills/testing.*/SKILL.mdto follow the repo's best practices
- Refer to skills in
- For bugs, add unit tests to check that the problem was present and then it's fixed (red/green approach)
- For renaming, make sure the entire code base is checked to make sure everything
is updated
- Follow
.claude/skills/coding.rename/SKILL.md
- Follow
- For change of function signature, make sure all the calling instances have been updated
Rank the Issues
- Reorder the issues in increasing complexity, starting from the issues with high confidence in the fix
Verification
-
tasks.mdcontains one issue block per input TODO - Every issue block has type, reason, proposed fix, confidence, complexity, and verification plan filled in
- Issues are ordered by increasing complexity, starting from the highest confidence fixes
- No code was changed, only the plan file was written
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.
- 29d ago Changed · -27 lines 89b2b2e840c7
- 1mo ago Changed · +10 lines · +3 tokens per session 55871e96f39f
- 1mo ago First seen · 80 lines · 7 tokens per session scan A e32ecfac8896
auto_task.create_specs_from_todos is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 589 once invoked, about $0.0000 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-09-08.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…