update-tracking

update-tracking is a skill for Claude Code, Codex from odarino/haren. It costs 11 tokens per session (472 once invoked), scanned A, original, MIT.

A progress-tracking tool that updates feature and module states in progress.json, a file that records project work. It also records status events and compares tracked commits with Git.

In plain words
What is it for?
Use it to change feature or module status, add features, reconcile progress with Git, and advance completed iterations when iteration tracking is enabled.
Why use it?
It prevents progress files, event logs, and Git history from falling out of sync as work moves between stages.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to change feature or module status, add features, reconcile progress with Git, and advance completed iterations when iteration tracking is enabled.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/odarino/haren/update-tracking
Install

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.

Any agent
npx skills add odarino/haren --skill update-tracking
Clone the repo
git clone --depth 1 https://github.com/odarino/haren

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for update-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/odarino/haren/update-tracking.svg)](https://agentmods.dev/skills/odarino/haren/update-tracking)
Your own site
<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>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 472 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 6891c75be27f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

content/skills/update-tracking/SKILL.md · 69 lines

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

  1. Validate the transition is allowed (see state machine in spec section 10)
  2. Update the feature's status in progress.json
  3. If all features in a module are "passing", suggest module completion review
  4. Append event to events/events.jsonl

Update Module Status

  1. Validate the transition is allowed
  2. Update the module's status and currentPhase
  3. Append event to events/events.jsonl

Add Feature to Module

  1. Add feature with "pending" status to the module's features map
  2. Update progress.json

Reconcile with Git

  1. For each repo, compare progress.json lastCommit against git HEAD
  2. If drift detected, warn user and update lastCommit
  3. Flag any ambiguous state changes for human review

Transition Iteration (only if iterations enabled)

  1. Check if all tasks in the current iteration have status "passing"
  2. If yes:
    • Increment currentIteration in progress.json
    • Update the iteration file (07-iterations/iteration-{N}.md) status to complete
    • 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
  3. 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)

Read the full file on GitHub · 69 lines

Changes

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.

  1. 8d ago First seen · 69 lines · 11 tokens per session scan A 6891c75be27f

Subscribe to this mod's changes

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.