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 odarino/haren --skill update-trackinggit clone --depth 1 https://github.com/odarino/harenWrote 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/odarino/haren/update-tracking)<a href="https://agentmods.dev/skills/odarino/haren/update-tracking"><img src="https://agentmods.dev/badge/skills/odarino/haren/update-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.00011 | $0.00472 |
| Opus 5 | $0.00005 | $0.00236 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
update-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 8d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Tracking
Update module and feature status in progress.json with validated transitions.
Operations
Update Feature Status
- Validate the transition is allowed (see state machine in spec section 10)
- Update the feature's status in progress.json
- If all features in a module are "passing", suggest module completion review
- Append event to events/events.jsonl
Update Module Status
- Validate the transition is allowed
- Update the module's status and currentPhase
- Append event to events/events.jsonl
Add Feature to Module
- Add feature with "pending" status to the module's features map
- Update progress.json
Reconcile with Git
- For each repo, compare progress.json lastCommit against git HEAD
- If drift detected, warn user and update lastCommit
- Flag any ambiguous state changes for human review
Transition Iteration (only if iterations enabled)
- Check if all tasks in the current iteration have status "passing"
- If yes:
- Increment
currentIterationin progress.json - Update the iteration file (
07-iterations/iteration-{N}.md) status tocomplete - If next iteration exists (already planned), set its status to
in-progress - If no next iteration exists, suggest running the plan skill to slice the next iteration from the master plan
- Append event to events/events.jsonl
- Increment
- Iteration transitions cannot be skipped — iteration N must complete before N+1 starts
Valid Module Transitions
discovered → decomposed → planned → implementing → evaluating → completed
↑ |
└── fix ───────┘
|
(3 failures)
↓
blocked
Valid Feature Transitions
pending → in-progress → evaluating → passing
→ fixing → evaluating (loop)
→ blocked (after 3 failures)
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.
- 8d ago First seen · 69 lines · 11 tokens per session scan A 6891c75be27f
update-tracking is a skill published in the GitHub repository odarino/haren (11 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 472 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-08-30.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.