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 bostonaholic/team --skill tracking-ticketsgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/tracking-tickets)<a href="https://agentmods.dev/skills/bostonaholic/team/tracking-tickets"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/tracking-tickets/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/bostonaholic/team/tracking-tickets"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/tracking-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00830 |
| Opus 5 | $0.00012 | $0.00415 |
| Sonnet 5 | $0.00005 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
tracking-tickets 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracking Tickets
Canonical tracker rules for pipeline pickup, PR linking, review state, and merge. Entry points keep only tracker-specific calls.
Best-effort, tracker-agnostic, never blocking
Every tracker interaction below is best-effort and tracker-agnostic: if the project defines no tracker-move mechanism (e.g. a free-form description with no ticket, or a tracker the environment cannot reach), skip silently and continue. Never block the pipeline on a tracker update.
Pickup: move the ticket to in-progress
When a run resolves its input to a ticket id or issue, move that ticket to its tracker's in-progress state. This is the first action of the run, before any other work begins.
PR open: link the PR to the ticket
When the PR phase opens a pull request and 1-task.md's frontmatter has
ticketId set, link the PR to the ticket. The tracker then closes
the ticket when the PR merges, and any board automation moves it to its
done state. On GitHub, render the link as a closing line emitted
as the final line of the PR body (Closes #<n>). For another
tracker use its PR↔issue link mechanism.
Interpreting ticketId
ticketId is interpreted where it is consumed — at PR-open time:
- A bare number →
Closes #<n>(a GitHub issue in the origin repo). - A qualified reference (
owner/repo#<n>) or an issue URL →Closesfollowed by that value substituted in — e.g.Closes https://github.com/owner/repo/issues/42. - Any other non-null shape still goes in verbatim as the footer text, as
Closesplus the value. Note the unrecognized shape in the completion report, and never block on it. On GitHub such a value (e.g.Closes ENG-1234) auto-closes nothing — the footer is then a legible reference only, and the tracker-move rules on this page are what advance the ticket. - Null, absent, empty, or whitespace-only → omit the closing line entirely. No placeholder, no empty footer.
Multi-repo: the home PR alone closes the ticket
In multi-repo mode, only the home repo's PR carries the closing
keyword (Closes #<n>). The ticket then closes exactly once, when the
home PR merges. Companion PRs carry a non-closing reference to the
issue in the same footer position, using the unambiguous qualified form
(owner/repo#<n> or the issue URL) — for example:
What ships with it
1 file 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.
- 4d ago Changed · -2 lines · -60 tokens per session 3ce43b54b588
- 5d ago First seen · 83 lines · 83 tokens per session scan A eefc2e6cd52e
tracking-tickets is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 830 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-09-03.
Other skills, from other repositories
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
pr-shepherding
Monitor PR lifecycle from creation through merge including CI monitoring, review comment handling, thread resolution, and merge readiness verification.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
gsd-tools
Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).