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 indranildchandra/claude-local-starter --skill aidlc-trackinggit clone --depth 1 https://github.com/indranildchandra/claude-local-starterWrote 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/indranildchandra/claude-local-starter/aidlc-tracking)<a href="https://agentmods.dev/skills/indranildchandra/claude-local-starter/aidlc-tracking"><img src="https://agentmods.dev/badge/skills/indranildchandra/claude-local-starter/aidlc-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/indranildchandra/claude-local-starter/aidlc-tracking"><img src="https://agentmods.dev/badge/skills/indranildchandra/claude-local-starter/aidlc-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.00031 | $0.00811 |
| Opus 5 | $0.00015 | $0.00405 |
| Sonnet 5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
aidlc-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 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIDLC Tracking
When to invoke this skill
- Before writing to any tracking file — load
formats.mdto get the exact template - Before running or suggesting
/compact— write a pre-compact snapshot first - When auto-compaction is detected — immediately write a pre-compact snapshot to
tasks/tracker.md - On
/init-repo— use formats to scaffold all tracking files; also runnpx gitnexus analyze
Tracking files and their purpose
| File | Purpose | Write rule |
|---|---|---|
docs/plan.md |
Architectural intent, before implementation | Append newest at TOP |
tasks/todo.md |
Live execution tracking during a session | Rewrite as work evolves |
tasks/tracker.md |
Append-only log of every task + session snapshot | Append newest at TOP |
audit/changelog.md |
What changed in the codebase, after implementation | Append newest at TOP |
docs/design-review.md |
Council review output from /design-review |
Append newest at TOP |
tasks/lessons.md |
Per-repo learning log, one entry per lesson learned | Append newest at TOP |
Core rules
- Never invent formats — always load
formats.mdfrom this skill before creating or appending to a tracking file - All files are per-repo — never write tracking files to a global location
- Create on first use — if a tracking file doesn't exist, create it with the header from
formats.md, then write the first entry below the header - Prepend, never append — for all append-only files (tracker, plan, changelog, lessons, design-review): insert each new entry immediately after the file header so the newest entry is always at the top. Never write to the end of the file. Only
todo.mdis rewritten wholesale. - Timestamps always use
YYYY-MM-DD HH:MM:SSformat
Pre-compact protocol
Before running /compact or when context auto-compaction is imminent:
- Invoke
/log-contextto write a pre-compact snapshot totasks/tracker.md - The snapshot must capture enough detail for a cold-start in the next session
- Then proceed with compaction
What ships with it
7 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.
- 9d ago First seen · 63 lines · 31 tokens per session scan A d3b1e5c5a0f9
aidlc-tracking is a skill published in the GitHub repository indranildchandra/claude-local-starter (13 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 811 once invoked, about $0.0002 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.