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 agentmods add skills/bostonaholic/team/principle-progress-trackingnpx skills add bostonaholic/team --skill principle-progress-trackinggit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/principle-progress-tracking)<a href="https://agentmods.dev/skills/bostonaholic/team/principle-progress-tracking"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/principle-progress-tracking.svg" alt="Measured on agentmods" 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.00023 | $0.00245 |
| Opus 5 | $0.00012 | $0.00122 |
| Sonnet 5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
principle-progress-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 today.
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.
What it actually says
Progress Tracking
A convention, not a gate: create no artifact and block nothing; expose progress so ordered steps cannot be silently skipped.
- For procedures with two or more ordered steps, seed one todo per step before starting; omit one-item ledgers.
- Without a todo tool, state the ledger once inline and name each step as it completes.
- Track numbered steps, not phases or files; for unnumbered procedures, track each natural unit such as a slice, question, or hard-gate finding, never each guidance sentence.
- Mark each item
in_progressat start andcompletedwhen landed, matchingteam-fix. - Let the orchestrator—the main Claude Code session—own one phase ledger.
- Let agents track skill sub-steps only inside their contexts; never merge or read across orchestrator and agent ledgers.
- Let directly invoked standalone skills own their ledgers.
- Apply
skills/qrspi-workflow/SKILL.mdfor the orchestrator TodoWrite phase-ledger contract.
What ships with it
1 file 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.
- today Changed · -28 lines · -26 tokens per session 5255291ca0ea
- 2d ago First seen · 47 lines · 49 tokens per session scan A 4f65dca63ae5
principle-progress-tracking is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 245 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-03.
Other skills, from other repositories
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
cog-weekly-reflection
Cross-domain pattern analysis with personal, professional, and project domain synthesis.
context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.