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 ntorga/agent-starter-kit --skill task-trackinggit clone --depth 1 https://github.com/ntorga/agent-starter-kitWrote 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/ntorga/agent-starter-kit/task-tracking)<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.
<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>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.00017 | $0.00948 |
| Opus 5 | $0.00009 | $0.00474 |
| Sonnet 5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
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.
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
-
Check for an existing to-do. Run
ls .memory/todo/ 2>/dev/nullto 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. -
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. TEMPLATEThen populate the items from
impl.mdepics 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. -
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.
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.
- 2d ago First seen · 86 lines · 17 tokens per session scan A 03fe241816fb
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.
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.
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.
gh
You have access to gh (GitHub CLI) for repository and project management.
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…
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.
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…