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 team-prgit 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/team-pr)<a href="https://agentmods.dev/skills/bostonaholic/team/team-pr"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-pr.svg" alt="Measured on agentmods" 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.00039 | $0.00712 |
| Opus 5 | $0.00019 | $0.00356 |
| Sonnet 5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
team-pr 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team PR — Create the Pull Request
Run the PR phase. Two modes:
- Resume mode — Implement passed the aggregate gate. The topic branch
has slice commits ready.
$ARGUMENTS/1-task.mdand$ARGUMENTS/6-design.mdexist. - Standalone mode — no matching artifact directory, but the working tree has commits or staged changes ready to ship. Treat the current branch as the work source.
Core contracts
- Update CHANGELOG.md and commit before opening any PR.
- Open a draft PR automatically — do not stop to ask. Push, then run
gh pr create --draft. - After creation, hand off to
/pr-watch-as-author. - In multi-repo mode, open one draft PR per repo and add
## Companion PRslinks. - Call the Skill tool with
tracking-ticketsfor the in-review transition and the multi-repo home-only closing rule. - After each push, refresh the body. Re-emit exactly one closing line: never duplicated, never dropped.
PR Body Template
## Summary
[What and why]
## Design Decisions
[Key decisions]
## Changes
[Observable changes]
## Screenshots
[Conditional]
## How to Verify
- [Verification performed]
## Pre-merge
[Conditional merge requirements]
## Review notes
[Conditional deferred findings]
## References
- Design: $ARGUMENTS/6-design.md
- Plan: $ARGUMENTS/8-plan.md
Closes #<n>
Prose bar. The body addresses one busy reader making one decision. Before finalizing, call the Skill tool with writing-prose and apply its ## One busy reader rule and its ## Self-lint. ## Summary opens with the recommendation or the observable outcome, never with a sentence describing the PR.
The Closes footer is conditional and appears as the final line of the PR body. Placement rationale: narrative precedes machine metadata. For ## Review notes, omit the section entirely when empty; never emit a bare heading. Tag COMMENT findings with their design-review-<n> source.
## Review notes (conditional): copy cross-model-notes.md with frontmatter stripped. Its copy replaces the final round's inline ### Cross-model disposition block; exclude ### Cross-model disposition from other sweeps so each round appears once.
What ships with it
7 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.
- 2d ago Changed · -360 lines · -113 tokens per session scan B → A 394e98e289d7
- 4d ago First seen · 439 lines · 152 tokens per session scan B 3a3ab0ad9a73
team-pr is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 712 once invoked, about $0.0002 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
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.
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.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.