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 hams-ollo/zen-agent-skills --skill quest-trackergit clone --depth 1 https://github.com/hams-ollo/zen-agent-skillsWrote 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/hams-ollo/zen-agent-skills/quest-tracker)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/quest-tracker"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/quest-tracker/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.
<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/quest-tracker"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/quest-tracker.svg" alt="Reviewed on agentmods" width="80" 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.00142 | $0.04906 |
| Opus 5.5 | $0.00057 | $0.01962 |
| Sonnet 5.5 | $0.00028 | $0.00981 |
| Haiku 4.5 | $0.00014 | $0.00491 |
Grade A, and why
quest-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 7d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quest-tracker
Run a season of work from one shared page. The page holds phases of steps, each step carrying what to do, why it matters, and what closes it, plus line ticks, facts written down on the way, a session log with screenshots, a quest chain, a burndown, and a People panel. Everything on it is drawn from one data block at the top of the page's script, and everything people do on it is saved in the page's own database, live, for everyone who can open it. At the top, a "Waiting on you" strip lists what needs a person: claims ready for a check, and stops the work has reached. Every tick says what it rests on: a command and its result, a claim without one, or a tick by hand.
The page is standalone: a published tracker needs nothing from this kit to run. This skill is what writes one, works against one, and lets agent sessions report into one without ever marking their own work done.
This skill is a draft. install.py places it under no profile until it has been used on real
work and blessed, per the contribution bar in the target repository's AGENTS.md. The tracker
pattern ran a whole client launch in October 2026 before it was a skill; claim-and-verify, the
waiting strip, and the evidence marks have not yet run on real work.
When to use
- A project or a season of work is starting and the person wants a tracker for it.
- A work session is starting or ending on a project that has a tracker, and the session should read what is next and record what it found.
- An agent or a child session has finished a step and should report it into the tracker.
- The person asks what is left, what is blocked, or what waits for them.
When not to use
- The host cannot publish a page with a shared database. See the decline path in step 0. Do not stand up a server, a database, or a file-based imitation instead.
- The question is about a repository's own task files. That is
sitrep, which reads them. - The work is already tracked in
.tasks/and the person has not asked for a tracker. A tracker is a working surface shared with people; it does not replace a backlog.
What ships with it
3 files 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.
- 7d ago First seen · 284 lines · 142 tokens per session scan A ec72ffc38bc6
quest-tracker 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,906 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-10-22.
Other skills, from other repositories
gsd-map-codebase
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents.
gsd-manager
Interactive command center for managing multiple phases from one terminal.
gsd-new-project
Initialize a new project with deep context gathering and PROJECT.md.
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
gsd-ns-context
Invoke this Pi skill with /skill:gsd-ns-context.
gsd-ns-project
Invoke this Pi skill with /skill:gsd-ns-project.