write-todos-skill

write-todos-skill is a skill for Claude Code from zeenie-ai/OpenCompany. It costs 21 tokens per session (797 once invoked), scanned A, original, MIT.

A structured task-list tool for breaking complex work into steps and tracking each step as pending, active, or done.

In plain words
What is it for?
Planning projects that take three or more steps, recording actionable tasks, and updating progress as work is completed.
Why use it?
It keeps multi-step work organised and shows what should happen next. It also makes progress visible instead of relying on memory.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Planning projects that take three or more steps, recording actionable tasks, and updating progress as work is completed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zeenie-ai/opencompany/write-todos-skill
Install

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.

Any agent
npx skills add zeenie-ai/OpenCompany --skill write-todos-skill
Clone the repo
git clone --depth 1 https://github.com/zeenie-ai/OpenCompany

Made for: Claude Code.

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.

agentmods badge for write-todos-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/zeenie-ai/opencompany/write-todos-skill/github.svg)](https://agentmods.dev/skills/zeenie-ai/opencompany/write-todos-skill)
Your own site
<a href="https://agentmods.dev/skills/zeenie-ai/opencompany/write-todos-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/write-todos-skill/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.

agentmods 80×15 button for write-todos-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/zeenie-ai/opencompany/write-todos-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/write-todos-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 797 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00797
Opus 5 $0.00010 $0.00398
Sonnet 5 $0.00004 $0.00159
Haiku 4.5 $0.00002 $0.00080

Measured 11d ago against content hash 576d83c27c95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

write-todos-skill 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 11d 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.

server/skills/assistant/write-todos-skill/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Task Planning with write_todos

You have access to the write_todos tool. Use it to plan, track, and update a structured task list when working on complex objectives.

When to Use

Use write_todos when the task requires 3 or more steps. Do NOT use it for trivial requests that you can complete in 1-2 tool calls.

How to Use

Follow this loop for every complex task:

1. Plan First

Before doing any work, call write_todos to create your plan. Break the objective into specific, actionable steps. Mark the first task in_progress immediately.

{
  "todos": [
    {"content": "Identify the relevant source files", "status": "in_progress"},
    {"content": "Implement the core logic", "status": "pending"},
    {"content": "Add error handling", "status": "pending"},
    {"content": "Verify the changes work", "status": "pending"}
  ]
}

2. Work, Then Update

After completing a step, call write_todos again with the updated list. Mark the finished task completed and the next task in_progress. Do this after every step -- do not batch updates.

{
  "todos": [
    {"content": "Identify the relevant source files", "status": "completed"},
    {"content": "Implement the core logic", "status": "in_progress"},
    {"content": "Add error handling", "status": "pending"},
    {"content": "Verify the changes work", "status": "pending"}
  ]
}

3. Revise as You Go

If you discover new work or a step becomes irrelevant, update the list. Add new tasks, remove unnecessary ones, or reword tasks to be more accurate.

{
  "todos": [
    {"content": "Identify the relevant source files", "status": "completed"},
    {"content": "Implement the core logic", "status": "completed"},
    {"content": "Fix unexpected edge case in parser", "status": "in_progress"},
    {"content": "Add error handling", "status": "pending"},
    {"content": "Verify the changes work", "status": "pending"}
  ]
}

4. Complete All Tasks

Keep working until every task is completed. Always have at least one task in_progress unless all are done.

Read the full file on GitHub · 93 lines

Changes

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.

  1. 11d ago First seen · 93 lines · 21 tokens per session scan A 576d83c27c95

Subscribe to this mod's changes

write-todos-skill is a skill published in the GitHub repository zeenie-ai/OpenCompany (880 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 797 once invoked, about $0.0001 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.