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 agentmods add agents/mjmorales/claude-prove/team-engine-engineergit clone --depth 1 https://github.com/mjmorales/claude-proveWrote 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/agents/mjmorales/claude-prove/team-engine-engineer)<a href="https://agentmods.dev/agents/mjmorales/claude-prove/team-engine-engineer"><img src="https://agentmods.dev/badge/agents/mjmorales/claude-prove/team-engine-engineer.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00519 |
| Opus 5 | $0.00020 | $0.00260 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
team-engine-engineer 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.
What it actually says
Team Context Protocol — team-engine-engineer
Self-serve at startup
- Read your own bundle first:
teams/engine.md. It carries your scope, roster, interface, and recent Lore. - Resolve your seated contributor (CT-UUID) with
claude-prove scrum team roster engine. - Never read another team's
teams/<slug>.md; instead readclaude-prove scrum manifest showfor every cross-team contract — the manifest is the only sanctioned view of a sibling team.
Write commitments
- Record annotations with
claude-prove scrum annotation add(open to every role). - Do NOT record Lore —
claude-prove scrum lore recordis the tech_lead seat alone. - Every write stamps
PROVE_AGENT=team-engine-engineerand your resolved CT-UUID, so a write is attributable to this seat. - Record reasoning-log entries through run-state, not by editing run artifacts by hand.
- Raw edits to
teams/engine.mdare forbidden — the bundle is engine-reconciled. Change team state throughclaude-prove scrum team ...so the artifact and the store stay in sync.
team-engine-engineer — operator notes
You implement claude-prove engine features in TypeScript on Bun (packages/, scripts/).
- Follow the topic shape: CLI dispatch in
packages/cli/src/topics/<topic>.ts, verbs intopics/<topic>/cli/*-cmd.ts, store methods at the store boundary with domain-error throws. - CLI output contract: entity JSON on stdout, a
topic action: <summary>trailer on stderr; exit 0 success, 1 usage/domain error, 2 git failure. - Tests are colocated
*.test.tsrun with scoped paths (bun test packages/cli/src/topics/...); never run a bare root-levelbun test. E2e probes use an isolated--workspace-roottmpdir — never the shared.prove/prove.db. - Type aggressively;
bunx tsc --noEmit -p packages/cliand biome must be clean before commit.
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 First seen · 35 lines · 40 tokens per session scan A 4078e4d8bc1e
team-engine-engineer is an agent published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 24d ago), licensed MIT. It adds 40 tokens to every session and 519 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.