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 atman-33/workhub --skill manage-backloggit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/manage-backlog)<a href="https://agentmods.dev/skills/atman-33/workhub/manage-backlog"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/manage-backlog.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.00057 | $0.00512 |
| Opus 5 | $0.00028 | $0.00256 |
| Sonnet 5 | $0.00011 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
manage-backlog 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 4d 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.
What it actually says
Manage the product backlog
The backlog is Markdown in the shared folder (SSoT):
projects/<p>/backlog/product-backlog.md (ordered overview) +
items/<id>-<slug>.md (one PBI = one file).
PBI file schema
---
id: P-0012 # per-project, sequential; next id = max existing + 1
title: ...
status: todo # todo | doing | review | done
points: 3 # from project.json sprint.pointScale
sprint: "" # sprint folder name once committed (plan-sprint sets it)
assignee: ""
repos: [] # repo names this PBI touches (from project.json)
created: <date>
updated: <date>
---
## Story
As a <user>, I want <capability>, so that <value>.
## Acceptance Criteria
- [ ] ...
## Tasks
- [ ] ...
## Notes
Operations
- Add: assign the next id, create
items/<id>-<slug>.md, add a row toproduct-backlog.mdat the position the user wants (order = table order). - Refine: fill missing story/AC/points; keep AC testable and concrete. Flag items that are vague or exceed the largest point value, and propose splits.
- Split: new ids for the parts; the original becomes
donewith a note pointing at its children, or is reworded as one of the parts. - Reorder / status: edit the overview table; status changes also update
the item file's frontmatter (
status,updated).doneis normally set by humans at review — don't mark items done unilaterally.
Rules
- Content in the team content language (
<content-language>);id/statusvalues stay as-is. - Never renumber existing ids. Never delete an item file — status and the overview table carry the lifecycle.
- Append one activity-log line summarizing the batch of edits.
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.
- 4d ago First seen · 59 lines · 57 tokens per session scan A dc0bac6dfb2e
manage-backlog is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 512 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
shipyard-executing-plans
Use when you have a written implementation plan to execute, either in the current session with builder/reviewer agents or in a separate session with review checkpoints. Also use when the user says "build this", "implement this", "execute the plan", "run the plan", or when a plan file has been loaded with independent…
shipyard-writing-plans
Use when you have a spec, requirements, or design for a multi-step task — before touching code. Also triggers on "plan this", "break this down", "create tasks", "decompose this feature", or when a task clearly needs more than 2-3 steps to implement. If you're about to start building without a plan, or writing vague…
shipyard-handoff
Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.