task-tracking

task-tracking is a skill for Claude Code, Codex from ntorga/agent-starter-kit. It costs 17 tokens per session (948 once invoked), scanned A, original, MIT.

A file-based to-do system for work that spans multiple steps or sessions. It stores unfinished items and progress in project files so a later session can resume.

In plain words
What is it for?
Tracking implementation tasks, plans, and checklists across hours or days. It helps create, update, and resume task lists.
Why use it?
It prevents progress from being lost when a session ends or the agent has no memory of earlier work. The next session can find the existing list instead of starting over.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Tracking implementation tasks, plans, and checklists across hours or days. It helps create, update, and resume task lists.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ntorga/agent-starter-kit/task-tracking
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 ntorga/agent-starter-kit --skill task-tracking
Clone the repo
git clone --depth 1 https://github.com/ntorga/agent-starter-kit

Made for: Claude Code, Codex.

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 task-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/ntorga/agent-starter-kit/task-tracking/github.svg)](https://agentmods.dev/skills/ntorga/agent-starter-kit/task-tracking)
Your own site
<a href="https://agentmods.dev/skills/ntorga/agent-starter-kit/task-tracking"><img src="https://agentmods.dev/badge/skills/ntorga/agent-starter-kit/task-tracking/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 task-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/ntorga/agent-starter-kit/task-tracking"><img src="https://agentmods.dev/badge/skills/ntorga/agent-starter-kit/task-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 948 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.00017 $0.00948
Opus 5 $0.00009 $0.00474
Sonnet 5 $0.00003 $0.00190
Haiku 4.5 $0.00002 $0.00095

Measured 2d ago against content hash 03fe241816fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-14, from the pricing page.

Security

Grade A, and why

task-tracking 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 2d 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.

skills/task-tracking/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Agents working on multi-step tasks need a way to track progress that survives session boundaries. A task that spans hours or days will be picked up by an agent with no memory of what was already done. This skill defines a file-based to-do format that any persona can create, update, and resume — so the next session starts where the last one stopped.

Procedure

  1. Check for an existing to-do. Run ls .memory/todo/ 2>/dev/null to list existing to-do files. If a to-do file for the current task already exists, read it and resume from the first unchecked item. Do not recreate.

  2. Create a to-do from the plan or task brief. If no existing to-do matches, run the following command to create the file — replace the placeholders with real values:

    mkdir -p .memory/todo && cat > .memory/todo/YYYY-MM-DD-<prefix>-<slug>.md << 'TEMPLATE'
    # <Task Title>
    
    **Slug:** <prefix>-<slug>
    **Source:** plan | task-brief
    **Created:** YYYY-MM-DD
    **Updated:** YYYY-MM-DD
    
    ## Items
    
    - [ ] First item
    - [ ] Second item
    
    ## Log
    
    - YYYY-MM-DD: Created from plan/task-brief.
    TEMPLATE
    

    Then populate the items from impl.md epics and file lists, or from the task brief's acceptance criteria. Each item must be a concrete, verifiable action — not a vague category.

    Target directory: .memory/todo/ — always at the project root, never anywhere else.

    Naming convention: The filename uses the pattern YYYY-MM-DD-<prefix>-<slug>.md, where <prefix> is the conventional-commit type and <slug> is a short kebab-case summary — the same convention used for branch names (follows: rules/git.md). Examples: .memory/todo/2026-02-18-feat-user-auth.md, .memory/todo/2026-02-18-fix-login-redirect.md. If a git branch already exists for this work, derive the prefix and slug from the branch name.

  3. Update as you go. After completing each item, mark it [x] and add a log entry if the outcome was notable (unexpected decision, deviation from plan, blocker encountered). Do not batch updates — mark items done as they finish.

Read the full file on GitHub · 86 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. 2d ago First seen · 86 lines · 17 tokens per session scan A 03fe241816fb

Subscribe to this mod's changes

task-tracking is a skill published in the GitHub repository ntorga/agent-starter-kit (142 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 948 once invoked, about $0.0001 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-09-13.

Related

Other skills, from other repositories

board

Read and write the workspace BOARD.md (shared task board for agents + Val). Wraps bin/board, a small Python CLI that preserves the markdown schema and appends to the activity log automatically. Use this whenever an agent proposes, claims, or finishes work that should be visible to the rest of the roster.

OpenCoven/coven · 66 tokens

squads-cli

Squads CLI — operate your AI workforce through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.

agents-squads/squads-cli · 53 tokens

gh

You have access to gh (GitHub CLI) for repository and project management.

agents-squads/squads-cli · 0 tokens

pm

Project Manager skill. One orchestrator session drives eight subagent roles -- planner, plan-reviewer, doer, reviewer, deployer, integ-test-runner, ci-watcher, harvester -- through cycles of Plan, Develop, Test, and Harvest across one or more parallel tracks in isolated git worktrees, running each task on a…

Apra-Labs/apra-fleet · 120 tokens

auto-sprint-args

How to construct and pass correct arguments to the auto-sprint workflow -- the required issues+branch fields, optional goal/maxcycles/basebranch/requirementsFile, JSON-object (not string) shape, and common launch mistakes. Trigger when preparing to launch or invoke auto-sprint.

Apra-Labs/apra-fleet · 61 tokens

fleet-sprint-cli

How to launch and supervise apra-fleet's autonomous sprint workflow from the CLI (apra-fleet workflow fleet-sprint) -- the --issue/--members/--branch/--base flag contract, the preconditions to check first, how to launch it as a detached process, and how to watch it via its dashboard. Trigger before running apra-fleet…

Apra-Labs/apra-fleet · 85 tokens