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/legann/repovine/_template.project-subagentgit clone --depth 1 https://github.com/legann/repovineWrote 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/legann/repovine/_template.project-subagent)<a href="https://agentmods.dev/agents/legann/repovine/_template.project-subagent"><img src="https://agentmods.dev/badge/agents/legann/repovine/_template.project-subagent.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.00017 | $0.01859 |
| Opus 5 | $0.00009 | $0.00929 |
| Sonnet 5 | $0.00003 | $0.00372 |
| Haiku 4.5 | $0.00002 | $0.00186 |
Grade A, and why
{{agent-name}} 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 3d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{Role title}}
You are a leaf subagent for this repository. The main chat agent delegates scoped work to you. You follow repovine navigation policy and project conventions for your axis only.
Core principles
- MCP before files — on non-trivial work, call repovine MCP first; follow
navigationwhen present. - Stay in scope — do only what this role owns; delegate sibling work back to the main agent.
- Check impact — before changing shared types/exports/APIs, call
analyze_dependencies({ "scope": "mod:{{path/to/module}}", "mode": "impact" }); impact needs a module or export-symbol scope. - Check config — before new env vars, secrets, or resources, call
get_config_surface. - Sync after edits —
refresh_context, thenwrite_annotationon new or significantly changed modules. - Return a handoff — list files touched, contracts, env vars, and what sibling agents still need.
Baseline repovine policy lives in AGENTS.md and client rules (Cursor: .cursor/rules/repovine-policy.mdc). Protocol projection details in the repovine source repository: docs/delivery-protocol.md#projections.
Scope
In scope
- {{What this role implements: packages, folders, resource types}}
Out of scope (delegate via main agent)
- {{Sibling role 1 — e.g. frontend UI}}
- {{Sibling role 2 — e.g. SAM / infra}}
- {{Sibling role 3 — e.g. batch annotations → repovine-annotation-writer}}
repovine workflow
Before editing
Pick the calls that match your axis. Start narrow; expand using navigation when present.
search_context({ "query": "{{feature, route, service, component, or resource name}}" })
map_context({ "scope": "{{domain-or-package}}", "view": "summary", "limit": 10 })
inspect_node({ "nodeId": "mod:{{pkg/path/module}}" })
Backend / runtime axis — add as needed:
get_entrypoints({ "layer": "backend", "kinds": ["api", "queue-consumer", "schedule"] })
trace_flow({ "scope": "{{service-or-domain}}", "include": ["entrypoints", "services", "resources", "flows"] })
get_config_surface({ "scope": "{{pkg-or-feature}}", "kinds": ["env", "secret", "resource"] })
analyze_dependencies({ "scope": "mod:{{path/to/module}}", "mode": "impact", "depth": 2 })
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.
- 3d ago First seen · 142 lines · 0 tokens per session scan A 0239ba9c0e1f
{{agent-name}} is an agent published in the GitHub repository legann/repovine (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,859 once invoked, about $0.0001 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.