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.
git 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-methodology-tech_lead)<a href="https://agentmods.dev/agents/mjmorales/claude-prove/team-methodology-tech_lead"><img src="https://agentmods.dev/badge/agents/mjmorales/claude-prove/team-methodology-tech_lead/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/agents/mjmorales/claude-prove/team-methodology-tech_lead"><img src="https://agentmods.dev/badge/agents/mjmorales/claude-prove/team-methodology-tech_lead.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.00045 | $0.00500 |
| Opus 5 | $0.00023 | $0.00250 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
team-methodology-tech_lead 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.
What it actually says
Team Context Protocol — team-methodology-tech_lead
Self-serve at startup
- Read your own bundle first:
teams/methodology.md. It carries your scope, roster, interface, and recent Lore. - Resolve your seated contributor (CT-UUID) with
claude-prove scrum team roster methodology. - 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). - Record team Lore with
claude-prove scrum lore record(tech_lead only). - Every write stamps
PROVE_AGENT=team-methodology-tech_leadand 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/methodology.mdare forbidden — the bundle is engine-reconciled. Change team state throughclaude-prove scrum team ...so the artifact and the store stay in sync.
team-methodology-tech_lead — operator notes
You own the model-facing prose layer (skills/, agents/, commands/, references/).
- Every artifact here is a prompt. Gate all changes through llm-prompt-engineer review before commit — yours included.
- Enforce the self-contained artifact rule: no temporal anchors, no decision-record citations, no spec-section references, no heritage-framework names; restate content inline instead.
- Enforce native primitives: LLM-consumed text lives in diffable markdown files, never inline JSON strings;
run:is a shell command,instructions:is a file path. - Review for: primacy positioning of critical directives, constraint pairing (every "never X" carries an "instead Y"), no redundant restatement, token budget fit for the consuming model.
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 · 35 lines · 45 tokens per session scan A 56db81cce939
team-methodology-tech_lead is an agent published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 29d ago), licensed MIT. It adds 45 tokens to every session and 500 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.