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 djangonavarro220/agentic-life-os --skill tasks-todogit clone --depth 1 https://github.com/djangonavarro220/agentic-life-osWrote 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/djangonavarro220/agentic-life-os/tasks-todo)<a href="https://agentmods.dev/skills/djangonavarro220/agentic-life-os/tasks-todo"><img src="https://agentmods.dev/badge/skills/djangonavarro220/agentic-life-os/tasks-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/djangonavarro220/agentic-life-os/tasks-todo"><img src="https://agentmods.dev/badge/skills/djangonavarro220/agentic-life-os/tasks-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.00023 | $0.00626 |
| Opus 5.5 | $0.00009 | $0.00250 |
| Sonnet 5.5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
tasks-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 2mo 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.
tasks-todo
Mandatory integrity contract
Before acting, load and follow ../../references/data-integrity.md. Its provenance, missing-value, correction-history, defensive-write, backup, and recovery rules are mandatory for this subskill.
Help the agent capture, clarify, prioritize, and review tasks without replacing the runtime's native task system by surprise.
Trigger
Use when the user wants to:
- capture a task
- review or prioritize tasks
- convert a vague intention into next actions
- decide what can be done now vs later
- inspect tasks suitable for a context, such as voice/walking/screen-free work
Task handling rules
For each task, distinguish:
- desired outcome
- next physical/digital action
- owner
- deadline or review date
- dependency/blocker
- context needed: screen, phone, errands, deep work, voice-only, waiting
If a task is vague, ask at most one lightweight clarification unless a safe default exists.
Integration policy
Runtime task systems stay runtime-owned unless the user explicitly chooses a different source. This skill may:
- discover where tasks live
- record task source decisions in
$LIFEOS_DATA_DIR/tasks-todo/data.json, including access instructions - read runtime/external tasks when the runtime exposes them
- write Life OS operational state such as last review time, priority scores, suppression windows, and caches
- propose task updates
- update runtime/external tasks only when the user explicitly asked and the runtime tool is available
Do not silently migrate all tasks into Life OS data. That is how you create a second todo swamp. Terrible idea.
Output contract
For capture:
Captured:
- Task: ...
- Next action: ...
- Context: ...
For review:
Tasks:
- Do now: ...
- Decide: ...
- Waiting: ...
- Later: ...
Install behavior
During install, do not globally register this subskill by default. If the user wants tasks-todo directly callable, ask first and handle it as a runtime adapter visibility decision. The helper does not record or perform global registration; it only creates private Life OS state containers.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 93 lines · 23 tokens per session scan A d17a13075ac1
tasks-todo is a skill published in the GitHub repository djangonavarro220/agentic-life-os (12 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 626 once invoked, about $0.0001 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
OpenSourceManagement
Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
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…
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…
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…