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/teejayen/arc/project-trackernpx skills add teejayen/arc --skill project-trackergit clone --depth 1 https://github.com/teejayen/arcWhat 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 | $0.00032 | $0.00552 |
| Opus 5 | $0.00016 | $0.00276 |
| Sonnet 5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
project-tracker 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Tracker
Track progress and status of projects and ventures.
When to Use
- Discussing any project
- Progress update or milestone reached
- Blocker identified or resolved
- Strategic thinking about projects
- Weekly review
Execution Steps
Step 1: Read current state
cat state/projects.json
Current structure:
{
"project_slug": {
"status": "ideation|building|launched|paused",
"tagline": "One-line description",
"next_milestone": "What's the immediate goal",
"blockers": ["blocker1", "blocker2"],
"recent_progress": ["item1", "item2"],
"updated": "YYYY-MM-DD"
}
}
Step 2: Determine update type
- Progress update: Something moved forward
- Blocker identified: New obstacle discovered
- Blocker resolved: Obstacle removed
- Milestone reached: Next milestone needs updating
- Status change: Major phase transition
- Strategic discussion: Thinking through direction
Step 3: Update projects.json
Make appropriate updates:
- Add to
recent_progress(keep last 5 items) - Update
blockersarray - Update
next_milestoneif reached - Update
statusif phase changed - Always update
updateddate
Step 4: Update area files if needed
For significant updates, also update:
areas/[project-name]/files
Step 5: Cross-reference
Note connections:
- Does this affect career planning?
- Time/resource implications for family?
- Learning opportunities to capture?
Step 6: Summarise
Provide current project status summary:
## Project Status
### [Project Name]
**Status:** [status]
**Next milestone:** [milestone]
**Blockers:** [blockers or "None"]
**Recent:** [last progress item]
### [Another Project]
**Status:** [status]
**Next milestone:** [milestone]
**Blockers:** [blockers or "None"]
**Recent:** [last progress item]
---
*Updated: YYYY-MM-DD*
State File Location
state/projects.json - source of truth for project status.
Area folders (areas/[project-name]/) contain deeper documentation, plans, and notes.
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 · 98 lines · 32 tokens per session scan A 1b246ac0ea26
project-tracker is a skill published in the GitHub repository teejayen/arc (5 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 552 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…