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-implementgit 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-implement)<a href="https://agentmods.dev/skills/bostonaholic/team/team-implement"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-implement/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-implement"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-implement.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.00026 | $0.00420 |
| Opus 5.5 | $0.00010 | $0.00168 |
| Sonnet 5.5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
team-implement 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 14d 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
Team Implement
Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema. 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. Relay completed reviewer reports unchanged.
Core contracts
- Require
7-structure.md,8-plan.md, and a non-default-branch worktree. UseAskUserQuestiononly for missing standalone setup. - If
4-repos.mdexists, multi-repo work requires worktrees; refuse in-place execution. - Seed TodoWrite with
Review round 1. - Retry as
Review round <n+1> (<b> Blocking, <m> Major open). - Read finding format before aggregate decisions.
- Persist
### Cross-model dispositiontocross-model-notes.mdonly when it does not beginNot run:. - Full pipeline: do not end the turn; call the Skill tool with
team-prin the same turn. - Standalone: after success, suggest
/team-pr.
Procedure references
Read each reference completely when reaching that stage. Follow them in order.
Applied principles
Read and apply: execution rules.
What ships with it
4 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.
- 14d ago Changed f00af49df6a2
- 24d ago Changed · -11 lines c4f4102a4ad3
- 28d ago Changed · -13 tokens per session b6e0aee7e7c3
- 1mo ago Changed · -1 lines 394f3dc7026d
- 1mo ago Changed · +6 lines e8be95b073f7
- 1mo ago Changed · +3 lines 4ca5fd464a98
- 1mo ago Changed · -207 lines · -66 tokens per session 266693582ad4
- 1mo ago First seen · 248 lines · 105 tokens per session scan A a4a3e4223eb8
team-implement is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed 12d ago), licensed MIT. It adds 26 tokens to every session and 420 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
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
quality-checklist
Validate implementation quality through custom checklists, scoring against constitution standards, specification coverage, and producing remediation recommendations.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.