Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add andreymudri/claude-teammates/plugin install claude-teammatesWrote 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/andreymudri/claude-teammates/phase-gate)<a href="https://agentmods.dev/skills/andreymudri/claude-teammates/phase-gate"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/phase-gate/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/andreymudri/claude-teammates/phase-gate"><img src="https://agentmods.dev/badge/skills/andreymudri/claude-teammates/phase-gate.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.00031 | $0.05493 |
| Opus 5 | $0.00015 | $0.02746 |
| Sonnet 5 | $0.00006 | $0.01099 |
| Haiku 4.5 | $0.00003 | $0.00549 |
Grade A, and why
phase-gate 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 9d 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Gate
Phases run autonomously end to end. The boundary is where verification happens.
Run it
node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" gate --run <runId> --root <project root> [--phase <name>]
Exit codes: 0 PASS, 1 FAIL, 2 the manifest is broken, 3 no manifest (an inferred one
was printed).
On exit 3, show the user the inferred manifest, get confirmation, and save it as
teammates.gate.json. Never invent checks silently.
Exit 2 is not a verdict — nothing was judged. teammates.gate.json is present and malformed,
and the message names the file and what is wrong with it. Show that message and stop; do not
re-run the gate, and never save an inferred manifest over the broken one, which would discard
the checks the operator meant to fix. complete and fix read the same manifest and exit 2
the same way.
Finish the pending checks
The CLI runs command checks itself and returns agent and mcp checks as pending —
those you execute:
-
agent — generate the dispatches rather than assembling them by hand:
node "$CLAUDE_PLUGIN_ROOT/scripts/cli.mjs" review-dispatch --run --root --phase [--models ]
It prints one reviewer per lens with the tier, effort, findings path, scratch worktree and prompt already resolved, and exits 4 rather than emitting a dispatch when the phase has no task branch to review. Every rule below is what it encodes; they are stated here because a dispatch assembled by hand still has to follow them.
Dispatch one
tm-reviewerper lens in parallel over the phase diff, without aname. A named reviewer becomes an addressable teammate that goes idle without emitting its result, and the review is lost; unnamed reviewers return normally. Six consecutive named dispatches were lost this way in runpreviewbefore the pattern was identified. Each dispatch carries the configured reviewer tier and effort, read withconfig get agents.reviewer.tierandconfig get agents.reviewer.effort.config geton an unset key exits 2 withunset: <key>— the same exit code every hard config failure uses, but here it is the normal case, not an error. The two keys fall back differently, and treating them alike is how a reviewer ends up judging below its guaranteed tier:unset: agents.reviewer.tier— dispatch at the fixed reviewer tier,capable(modelopus, per the tier→model map inparallel-execution— remap there and this line follows). Never omit the model to inherit the session's: in amidsession that would have the reviewer grading everyagentcheck a full tier below what this skill guarantees. A configured tier replacescapable; nothing else does.unset: agents.reviewer.effort— omit theeffortoption, and the dispatch inherits the session's effort. Only effort falls back this way.
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.
- 9d ago First seen · 337 lines · 31 tokens per session scan A 6bef7cb995c4
phase-gate is a skill published in the GitHub repository andreymudri/claude-teammates (2 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 5,493 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-08-31.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
verify-dotnet-samples
How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.
regex-tester
Validate, test, and debug regular expressions by executing them against sample inputs. Use when asked to build, verify, or explain a regex pattern.