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 start-pbigit 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/start-pbi)<a href="https://agentmods.dev/skills/atman-33/workhub/start-pbi"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/start-pbi/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/atman-33/workhub/start-pbi"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/start-pbi.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.00055 | $0.00372 |
| Opus 5.5 | $0.00022 | $0.00149 |
| Sonnet 5.5 | $0.00011 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
start-pbi 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 1mo 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
Start a PBI
The branch-naming convention is enforced here, at the moment work begins —
it is what later links merged code back to the PBI
(sync-project-repos.mjs extracts ids from merge subjects).
Steps
- Resolve the project and PBI (by id like
P-0012, or by title search inbacklog/items/). - Update the PBI file:
status: doing,assignee: <me>(from<team-context>),updated: <date>; mirror the status inproduct-backlog.md. - Issue the branch name:
pbi/<id-lowercase>-<slug>(e.g.pbi/p-0012-user-login), slug from the item filename. State it clearly and remind: merge/PR titles into the project's dev-main branch must carry the id (branch name or a[P-0012]tag). - If asked, create the branch in the user's own checkout of the relevant
repo (
reposfrontmatter / project.json), cut from the project's devMainBranch — never in the script-owned mirror underrepoWorkspacesRoot. - Append an activity-log line
(
- <date> [<agent>/<me>] start-pbi: P-0012 → doing, branch pbi/p-0012-...).
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.
- 1mo ago First seen · 29 lines · 55 tokens per session scan A f5d3e6766c31
start-pbi is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 372 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
session-end
Use this skill when performing a full session close-out: verifies all planned work against the agreed plan, creates issues for gaps, runs quality gates, commits cleanly, mirrors to GitHub, and produces a session summary. Triggered by /close command.
session-start
Use this skill when initializing a session for any project repo. Autonomously analyzes git state, VCS issues, SSOT files, branches, environment, and cross-repo status. Then presents structured findings with recommendations before development wave planning, or an operations contract for explicitly requested…
close
End session with verification, commits, and documentation.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.
daily-handoff
Create a concise, durable end-of-day handoff for one or more tracked production tasks, covering status, completed work, changed systems, verification evidence, blockers, next commands, and commit state. Use when the user invokes $daily-handoff, asks for today's multi-task handoff, or needs a compact file-backed…