init-worktracking

init-worktracking is a skill for Claude Code, Codex from hams-ollo/zen-agent-skills. It costs 142 tokens per session (4,537 once invoked), scanned A, original, MIT.

A setup tool that adds a file-based work-tracking system to a repository, including shared agent rules and small task files. It can also add a roadmap, changelog, validation checker, and pointers for different coding agents.

In plain words
What is it for?
Use it to organize work into assignable tasks, record dependencies and acceptance checks, and guide agents to the right project instructions.
Why use it?
It gives agents focused instructions and limits the files they need to read or change, which helps keep tasks manageable.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it to organize work into assignable tasks, record dependencies and acceptance checks, and guide agents to the right project instructions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hams-ollo/zen-agent-skills/init-worktracking
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 hams-ollo/zen-agent-skills --skill init-worktracking
Clone the repo
git clone --depth 1 https://github.com/hams-ollo/zen-agent-skills

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 init-worktracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/init-worktracking/github.svg)](https://agentmods.dev/skills/hams-ollo/zen-agent-skills/init-worktracking)
Your own site
<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/init-worktracking"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/init-worktracking/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.

agentmods 80×15 button for init-worktracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/init-worktracking"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/init-worktracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 142 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,537 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.00142 $0.04537
Opus 5.5 $0.00057 $0.01815
Sonnet 5.5 $0.00028 $0.00907
Haiku 4.5 $0.00014 $0.00454

Measured 7d ago against content hash d7e9372af9ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

init-worktracking 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 7d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (templates/validate.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/init-worktracking/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

init-worktracking

Scaffold a spec-driven, low-context-bloat work-tracking system into whatever repository this is invoked from. The system is separate files at four altitudes of work, so an assigned agent loads only what its task needs:

  • AGENTS.md - global rules, including the agent reading protocol (read this file + your one task file + only its touched_files).
  • .tasks/ - atomic, agent-assignable task files, one per work item, with done/ for completed ones and a shipped validate.py.
  • ROADMAP.md - the strategic Epic/Feature layer.
  • CHANGELOG.md - append-only ledger of finished tasks.
  • CLAUDE.md, which imports AGENTS.md with @AGENTS.md, and optional Cursor/Copilot files that point at it: AGENTS.md is the one canonical source every agent flavor reads.

Templates live in templates/. Fill their {{PLACEHOLDERS}} from the actual repo and write them in, without clobbering anything that already exists.

Why this shape

The point is context frugality for agents. A task file's touched_files frontmatter is a read/write whitelist, depends_on is a safe-dispatch guard for parallel agents, and the acceptance criteria are a mechanically checkable command the agent self-verifies against. That is exactly the unit the fix-batch skill consumes: one task file per parallel worktree-isolated agent, and the unit the new-task skill authors. So the scaffold is only as good as the honesty of those fields, which is why a validator ships with it.

Footprint tiers

Do not dump the whole system on a 200-line project. Ask which tier fits, or infer from repo size and let the user correct:

Tier Writes For
lite AGENTS.md, .tasks/ (README, _TEMPLATE.md, validate.py, done/), CLAUDE.md pointer small or solo repos that want task files without the ceremony
standard lite + ROADMAP.md + CHANGELOG.md most repos; the full altitude model
team standard + a CI/pre-commit invocation of the validator + optional Cursor/Copilot pointers repos with many contributors or agents, where drift must be caught mechanically

Read the full file on GitHub · 186 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. 7d ago Changed · -3 lines · -65 tokens per session d7e9372af9ea
  2. 1mo ago Changed · +7 lines 8089e4d31d11
  3. 2mo ago First seen · 182 lines · 207 tokens per session scan A 1424bb6f9ef5

Subscribe to this mod's changes

init-worktracking is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 142 tokens to every session and 4,537 once invoked, about $0.0006 per session on Opus 5.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.