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 protonium-labs/axiomcore-plugin --skill todosgit clone --depth 1 https://github.com/protonium-labs/axiomcore-pluginWrote 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/protonium-labs/axiomcore-plugin/todos)<a href="https://agentmods.dev/skills/protonium-labs/axiomcore-plugin/todos"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/todos/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/protonium-labs/axiomcore-plugin/todos"><img src="https://agentmods.dev/badge/skills/protonium-labs/axiomcore-plugin/todos.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.00066 | $0.02906 |
| Opus 5 | $0.00033 | $0.01453 |
| Sonnet 5 | $0.00013 | $0.00581 |
| Haiku 4.5 | $0.00007 | $0.00291 |
Grade A, and why
todos 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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Execute the requested action: $ARGUMENTS
Calling rule: /todos <action> <arguments>.
Module check: read axiom-config.md. If M3-todos is inactive, reply in one line that the module is inactive and offer /axiom activate M3 — execute nothing. Note the mode: vault-only or notion.
If the requested action is ambiguous or contradictory, do NOT guess: flag the ambiguity and ask for clarification before executing.
Core principles (To-Do Protocol, root CLAUDE.md):
- The task list is the user's to-do list — only tasks the user acts on become task lines/cards.
- Confirmation gate: never create a task for the user without explicit approval. Propose short name + description, wait for OK, only then allocate the ID and write the line.
- Agent tasks (my own work items) live under a
## Agentheading at the end of the WP'stasks.md— IDs like any task, never mirrored externally. - One task may bundle several items. A task is one line with an ID and a short name; the individual points go into the description, not into separate tasks. Bundle vs. split: see the format section.
- Reference, don't restate. Where the detail already lives in a deliverable or vault page, the description summarises each point in a line or two and points at the document.
- Notion mode only: board wins status, vault wins wording. Card descriptions are write-once at creation. Sync is on-demand only. Cards mirror task lines in WP
tasks.mdfiles only — never structural pages.
Mode behavior
| Action | vault-only | notion |
|---|---|---|
new, status |
Full function | Full function |
sync, push, pull, board |
One-line reply: needs the Notion mirror — offer to check for the connector and switch modes | Full function |
If the mode is vault-only but a Notion connector is detected during any action, mention once that the Kanban mirror is available (/axiom activate M3 handles the switch); do not switch silently.
If action is empty
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.
- 10d ago First seen · 150 lines · 66 tokens per session scan A d765e5168712
todos is a skill published in the GitHub repository protonium-labs/axiomcore-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 2,906 once invoked, about $0.0003 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
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…
matter-workspace
Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when…
manage-glue-workers
Use when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how…
commitments
Use to track what the user has promised — to their manager, execs, partner teams — and to keep those promises from silently going stale. Trigger phrases include "what have I committed to", "add a commitment", "I promised X by Friday", "am I overcommitted", "help me say no to this", "I need to renegotiate a deadline".…
recipe-plan
Create work plan from design document and obtain plan approval.
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…