todos

todos is a skill for Claude Code from DavidROliverBA/ArchitectKB. It costs 0 tokens per session (541 once invoked), scanned A, original, MIT.

A set of rules for managing a Claude Code todo list during an active work session.

In plain words
What is it for?
Use it to decide which tasks belong in the current-session todo list and which should be stored as dated task notes or handled elsewhere.
Why use it?
It keeps immediate work separate from future reminders and completed items, so the list stays focused.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter. Also seen: mentions Claude Code.

Good fit Use it to decide which tasks belong in the current-session todo list and which should be stored as dated task notes or handled elsewhere.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davidroliverba/architectkb/todos
Install

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.

Any agent
npx skills add DavidROliverBA/ArchitectKB --skill todos
Clone the repo
git clone --depth 1 https://github.com/DavidROliverBA/ArchitectKB

Made for: Claude Code.

Wrote 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.

agentmods badge for todos

README.md
[![agentmods](https://agentmods.dev/badge/skills/davidroliverba/architectkb/todos/github.svg)](https://agentmods.dev/skills/davidroliverba/architectkb/todos)
Your own site
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/todos"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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.

agentmods 80×15 button for todos

Your own site · 80×15
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/todos"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/todos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00541
Opus 5 $0.00000 $0.00270
Sonnet 5 $0.00000 $0.00108
Haiku 4.5 $0.00000 $0.00054

Measured 9d ago against content hash e4e87ed121eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 9d 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.

.claude/skills/todos/SKILL.md · 93 lines

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.

Skill: Todo List Management

Guidelines for managing the Claude Code todo list during sessions.

Core Principles

1. Only Track Active Work

The todo list should only contain:

  • Tasks currently in progress
  • Tasks to be done in the current session
  • Recently completed tasks (for context)

2. Future-Dated Tasks

Do NOT add future-dated tasks to the todo list.

Tasks with due dates in the future should:

  • Be stored in the vault as Task notes (using /task skill)
  • Be tracked in Jira/external systems
  • Only appear in the todo list on or after their due date

Why: The todo list is for immediate work tracking, not a calendar or reminder system.

3. When to Add Tasks

Add to todo list when:

  • User explicitly asks you to do something now
  • Breaking down a complex current task into steps
  • Tracking multi-step work in the current session

Do NOT add when:

  • Task is scheduled for a future date
  • Task is a reminder/calendar item
  • Task belongs in an external system (Jira, calendar)

4. Cleaning Up

Regularly clean the todo list:

  • Remove completed tasks after they're no longer relevant for context
  • Remove tasks that have been deferred to future dates
  • Keep the list focused on current work

Examples

Good Usage

User: "Help me refactor the authentication module"

Todo list:
- [in_progress] Analyse current auth module structure
- [pending] Identify refactoring opportunities
- [pending] Implement changes
- [pending] Update tests

Bad Usage

User: "Remind me to review the ADR process in April"

❌ Don't add: [pending] Review ADR process (due 2026-04-07)
✅ Do: Create a Task note with due date, or note it will surface when due

Integration with Task Notes

For future tasks, use the /task skill instead:

/task Review ADR process due 2026-04-07

This creates a proper Task note in the vault that can be:

  • Queried by Dataview
  • Shown in daily notes when due
  • Tracked properly with full metadata

Summary

Task Type Where to Track
Current session work Todo list
Today's tasks Todo list
Future dated Task note in vault
Recurring reminders Task note or calendar
Project work items Jira + Task notes

Read the full file on GitHub · 93 lines

Changes

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.

  1. 9d ago First seen · 93 lines · 0 tokens per session scan A e4e87ed121eb

Subscribe to this mod's changes

todos is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 541 tokens. 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-09-03.

Related

Other skills, from other repositories