Borrowing it
Nothing to install: this file belongs to legann/repovine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/legann/repovine/main/.agents/skills/repovine-workflow/SKILL.mdgit 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/skills/legann/repovine/repovine-workflow)<a href="https://agentmods.dev/skills/legann/repovine/repovine-workflow"><img src="https://agentmods.dev/badge/skills/legann/repovine/repovine-workflow/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/legann/repovine/repovine-workflow"><img src="https://agentmods.dev/badge/skills/legann/repovine/repovine-workflow.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.00035 | $0.04100 |
| Opus 5 | $0.00017 | $0.02050 |
| Sonnet 5 | $0.00007 | $0.00820 |
| Haiku 4.5 | $0.00003 | $0.00410 |
Grade A, and why
repovine-workflow 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 8d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Workflow
Use this skill when implementing a change and the project-specific conventions are not encoded in a local skill yet.
repovine does not decide how this repository should build backend, frontend, or infrastructure code. It gives the agent a repeatable way to understand the repository before changing it, then verify the result after editing.
Relationship to Subagent Orchestration
This workflow scopes a repo change and verifies it after edits.
You are the main agent. Use the active client's native agent surface for delegation.
The default implementer after repovine setup is project-subagent-sample. Specialist agents are repo-owned copies of _TEMPLATE.project-subagent.*. Agent identity comes from frontmatter/TOML name, not filename.
Delegation policy:
- Non-trivial implementation: delegate to project-subagent-sample unless the user named project subagents or explicitly asked the main chat to implement.
- One named subagent: use only that agent.
- Two or more named subagents: use exactly the named set; do not add the default unless named.
- Parallel runs only for disjoint scopes; leaf subagents never call each other. Exception: never parallelize annotation writes —
repovine-annotation-writerand any agent callingwrite_annotationrun one at a time, even across disjoint module scopes, because every write goes through one debounced annotation store (parallel writers gain no throughput and can lose annotations). - Main chat stays direct for trivial edits and questions; route utility work to
repovine-repo-explorer,repovine-annotation-writer,repovine-architecture-auditor, orrepovine-code-reviewerwhen that specialist fits. - Architecture audits use
repovine-architecture-auditor; read-only implementation/diff reviews userepovine-code-reviewer.
Handoffs must include scope, acceptance criteria, contracts, prior handoff context, files/nodes touched, tests, and blockers. Run refresh_context between dependent phases after graph-relevant edits. After feature work, use repovine-workflow for post-edit verification or repovine-review for read-only review, then repovine-annotations in touched scope — Drain the annotation queue in batches until needsWork: 0 (includes propagation-stale with staleKind: "propagation").
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.
- 8d ago First seen · 175 lines · 35 tokens per session scan A 3034200d9c74
repovine-workflow is a skill published in the GitHub repository legann/repovine (0 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 4,100 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…