Borrowing it
Nothing to install: this file belongs to poteto/noodle. 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/poteto/noodle/main/.agents/skills/todo/SKILL.mdgit clone --depth 1 https://github.com/poteto/noodleWrote 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/poteto/noodle/todo)<a href="https://agentmods.dev/skills/poteto/noodle/todo"><img src="https://agentmods.dev/badge/skills/poteto/noodle/todo/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/poteto/noodle/todo"><img src="https://agentmods.dev/badge/skills/poteto/noodle/todo.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.00061 | $0.00394 |
| Opus 5.5 | $0.00024 | $0.00158 |
| Sonnet 5.5 | $0.00012 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00039 |
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 1mo 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
Manage the project backlog at brain/todos.md. Edit the file directly with Edit/Write tools.
File Format
# Todos
<!-- next-id: 26 -->
## Section Name
1. [x] Completed item description
2. [ ] Open item description [[plans/02-some-plan/overview]]
- Items are numbered markdown checkboxes:
N. [ ] descriptionorN. [x] description - Sections are
## Headinggroups <!-- next-id: N -->tracks the next available ID
Operations
Add an item
- Read
<!-- next-id: N -->to get the next ID - Append
N. [ ] descriptionto the target section - Increment the next-id marker:
<!-- next-id: N+1 -->
Mark done
Change [ ] to [x] and update the description with a reason:
2. [x] Old description — superseded by #75 channel UI redesign
Then move the done item from brain/todos.md to brain/archive/todos.md (create the file if it doesn't exist). Remove empty sections left behind.
Edit description
Replace the description text. Preserve any [[wikilinks]] unless intentionally removing them.
Rules
- IDs are permanent. Never renumber or reuse them.
- Always increment
<!-- next-id -->when adding items. - Keep items in their section — don't move between sections without being asked.
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.
- 1mo ago First seen · 57 lines · 61 tokens per session scan A ab472cbc4b92
todo is a skill published in the GitHub repository poteto/noodle (529 stars, last pushed 7mo ago), licensed MIT. It adds 61 tokens to every session and 394 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…