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 zeenie-ai/OpenCompany --skill write-todos-skillgit clone --depth 1 https://github.com/zeenie-ai/OpenCompanyWrote 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/zeenie-ai/opencompany/write-todos-skill)<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.
<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>- NVIDIA SkillSpector pass
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.00021 | $0.00797 |
| Opus 5 | $0.00010 | $0.00398 |
| Sonnet 5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
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.
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.
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.
- 11d ago First seen · 93 lines · 21 tokens per session scan A 576d83c27c95
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.
Other skills, from other repositories
imsg
Use the imsg CLI from OpenClaw agents for iMessage/SMS DMs, groups, replies, reactions, polls, watching, and private-API actions.
control-ui
Operate and troubleshoot the OpenClaw Control UI: navigate connected clients, organize sessions, build session dashboards, and handle direct or Tailscale-hosted Gateways.
gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
taskflow-inbox-triage
Preview synthetic inbox routing with a real TaskFlow approval pause, and identify the adapters needed for live triage.
wacli
Send third-party WhatsApp messages or sync/search WhatsApp history via wacli, not normal active chats.