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 agentmods add skills/aksika/abtars/todonpx skills add aksika/abtars --skill todogit clone --depth 1 https://github.com/aksika/abtarsWrote 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/aksika/abtars/todo)<a href="https://agentmods.dev/skills/aksika/abtars/todo"><img src="https://agentmods.dev/badge/skills/aksika/abtars/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.00007 | $0.00232 |
| Opus 5 | $0.00003 | $0.00116 |
| Sonnet 5 | $0.00001 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
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 5d 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.
What it actually says
Todo Skill
Manage a persistent todo list via shell commands.
Commands
abtars-todo add "description"— add new itemabtars-todo list— show all itemsabtars-todo done <N>— mark item N as completeabtars-todo remove <N>— delete item N
Item numbers are 1-based, in the order they appear in the file.
When to use
- User says "remind me", "don't forget", "add to my list", "todo", "emlékeztess", "ne felejtsd"
- User asks "what's on my list", "what do I need to do", "mi van a listámon"
- After completing a task the user previously asked to track
When NOT to use
- For time-specific reminders with a specific date/time (use abtars-cron instead)
- For facts/preferences (use abmind store instead)
- For routine conversational messages
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.
- 5d ago First seen · 31 lines · 7 tokens per session scan A e96916d2a615
todo is a skill published in the GitHub repository aksika/abtars (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 7 tokens to every session and 232 once invoked, about $0.0000 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-31.
Other skills, from other repositories
personal-assistant
A personalized assistant that remembers your preferences.
file-organizer
Organizes files in your project directory.
simple
Summarize short user notes into clear action items.
context-optimizer
Analyze skill content for optimal placement (Skill vs Passive Context vs Hybrid), compress markdown to pipe-delimited format (60-80% token reduction), and validate compliance against the decision framework. Passive context wins for what the model cannot know (post-cutoff APIs, repo gotchas); pre-trained knowledge…
analysis-provenance
Identify code ownership before modifying validators or linters. Checks file headers for provenance indicators, reviews documentation, and determines provenance as UPSTREAM, LOCAL, VENDOR, or UNKNOWN. Prevents accidental modification of upstream tools.
panning-for-gold
Triage raw unstructured input (transcripts, brain dumps) into evaluated thread inventories and a synthesized gold-found file. Four phases: front-gate, extract, evaluate, synthesize. Use when you say "pan for gold", "triage transcript", "synthesize gold-found", or hand it a voice transcript or brain dump. Do NOT use…