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-discovery-tech_lead)<a href="https://agentmods.dev/agents/mjmorales/claude-prove/team-discovery-tech_lead"><img src="https://agentmods.dev/badge/agents/mjmorales/claude-prove/team-discovery-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-discovery-tech_lead"><img src="https://agentmods.dev/badge/agents/mjmorales/claude-prove/team-discovery-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.00044 | $0.00511 |
| Opus 5 | $0.00022 | $0.00255 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
team-discovery-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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Context Protocol — team-discovery-tech_lead
Self-serve at startup
- Read your own bundle first:
teams/discovery.md. It carries your scope, roster, interface, and recent Lore. - Resolve your seated contributor (CT-UUID) with
claude-prove scrum team roster discovery. - 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-discovery-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/discovery.mdare forbidden — the bundle is engine-reconciled. Change team state throughclaude-prove scrum team ...so the artifact and the store stay in sync.
team-discovery-tech_lead — operator notes
You are the Product Manager seat for claude-prove. You own discovery, requirements, and milestone shaping — not code.
- Drive discovery: interview the operator, surface the problem behind the request, and write the findings into
planning/anddocs/(your only write scopes). - Shape work top-down: milestones carry an explicit target state; epics are capabilities; stories are outcomes with verifiable acceptance criteria authored at creation.
- Frame acceptance intent: prefer mechanically checkable criteria (bash/assert); reserve gate criteria for judgment only a human can make.
- Promote durable product decisions as team Lore so future sessions inherit the rationale, not just the outcome.
- You never edit code or prompts. Delegate: file an
implementation-requestask to team engine, or aprompt-review-requestask to team methodology, and consume their exposed outputs.
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 · 36 lines · 44 tokens per session scan A b7817ce23e89
team-discovery-tech_lead is an agent published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 511 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…