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/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/team-pr"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-pr.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.00028 | $0.00645 |
| Opus 5.5 | $0.00011 | $0.00258 |
| Sonnet 5.5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
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 yesterday.
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team PR — Create the Pull Request
Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading.
Before finalizing prose you author, read the writing standards; for the PR body, apply its ## One busy reader rule and its ## Self-lint. Preserve exact commands, tokens, and templates.
Two modes:
- Resume mode —
$ARGUMENTS/1-task.mdand$ARGUMENTS/6-design.mdexist. Execution step 3 binds one review status from the newestreview-<n>.mdand one security status from the newestsecurity-review-<n>.md. - Standalone mode — no matching artifact directory, but the working tree has commits or staged changes ready to ship. The current branch is the work source.
Core contracts
Each is detailed in Execution at the step named.
- Update an existing CHANGELOG.md after step 3 binds the review and security statuses, and commit before opening any PR; never create one unrequested (step 6).
- Open a draft PR automatically — do not stop to ask (step 7), then report it and how to mark it ready for review.
- Multi-repo: one draft PR per repo, with
## Companion PRslinks. Tracking rules own the in-review transition and the home-only closing rule. - After each push, refresh the body with exactly one closing line: never duplicated, never dropped (step 10).
- A branch that impacts a UI always carries screenshots (step 4).
- Deferred findings and cross-model dispositions are comments on the home PR, never the body: run review comments after open and after each refresh; a refresh posts only missing comments.
- Subagents and inline work split per Execution
## Step dispatch.
Apply the body authoring rules to initial drafts and every refresh.
What ships with it
25 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.
- agents/openai.yaml 179 B
- references/01-input.md 1.8 KB
- references/02-execution.md 7.6 KB
- references/03-pr-body-template.md 5.5 KB
- references/04-screenshot-upload.md 4.2 KB
- references/05-changelog-update.md 206 B
- references/06-commit-discipline.md 527 B
- references/07-review-comments.md 4.3 KB
- references/changelog.md 3.4 KB
- references/commit.md 1.7 KB
- references/screenshot-input-and-result.md 5.3 KB
- references/screenshot-rejected-approaches.md 918 B
- references/screenshot-rules.md 4.0 KB
- references/screenshot-upload-and-body-edit.md 7.2 KB
- references/screenshot-verify.md 3.4 KB
- references/tracking.md 2.3 KB
- scripts/changelog-candidates.mjs 6.3 KB runs code
- scripts/manifest-entries.mjs 6.9 KB runs code
- scripts/pre-image.sh 2.9 KB runs code
- scripts/resolve-pr.sh 5.9 KB runs code
- scripts/review-comments.mjs 7.7 KB runs code
- scripts/ship-state.sh 1.5 KB runs code
- scripts/splice.mjs 39 KB runs code
- scripts/upload.sh 15 KB runs code
- scripts/write-companion.sh 6.3 KB runs code
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.
- yesterday Changed · -5 lines b6e0e8c07a56
- 15d ago Changed · +1 lines 63e23ca51c1d
- 16d ago Changed 8237c20c63ec
- 21d ago Changed · +2 lines f035d4c8cbf3
- 26d ago Changed · -40 lines 6c8fa6e1f22e
- 1mo ago Changed · -16 tokens per session 7b5f9310f762
- 1mo ago Changed · +2 lines 3825e37b0b03
- 1mo ago Changed · +4 lines · +5 tokens per session 379e5d940d4b
- 1mo ago Changed · +1 lines 1a8790f996b9
- 1mo ago First seen · 84 lines · 39 tokens per session scan A afdb097bc07f
team-pr is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 645 once invoked, about $0.0001 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
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.