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 skills/gomilesf/convergo/cvg-build-loopnpx skills add gomilesf/convergo --skill cvg-build-loopgit clone --depth 1 https://github.com/gomilesf/convergoWrote 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/gomilesf/convergo/cvg-build-loop)<a href="https://agentmods.dev/skills/gomilesf/convergo/cvg-build-loop"><img src="https://agentmods.dev/badge/skills/gomilesf/convergo/cvg-build-loop.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.1 | $0.00049 | $0.02388 |
| Opus 5 | $0.00024 | $0.01194 |
| Sonnet 5 | $0.00010 | $0.00478 |
| Haiku 4.5 | $0.00005 | $0.00239 |
Grade A, and why
cvg-build-loop 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 6d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Loop
Use this skill for implementation work that should be executed by a monitored specialist worker and reviewed by monitored specialist reviewers.
Before doing anything, open and read references/cvg-multi-session-protocol.md, then apply the protocol gates from cvg-multi-session:
- transport binding gate,
- real specialist session gate,
- orchestrator callback transport gate,
- waiting handoff gate,
- cvg-code-review-feedback gate,
- fresh-reviewer exit gate.
Phase 0: Orchestrator Setup
Record:
- current orchestrator session id (Codex thread id; on Claude Code the harness tracks it),
- implementation base commit with
git rev-parse HEAD, - worktree status,
- task-owned and unrelated dirty files,
- source artifact or implementation goal,
- allowed external side effects, if any,
- the loop ledger path, created per the Gate 5 loop-ledger rule.
Pass unrelated dirty state to the worker and tell it not to overwrite those files.
If the plan's slices or invariant matrix span multiple repos, declare the repo split and build order to the user before spawning the worker, and scope this loop to one repo's slices: the loop's base/head and diff bookkeeping covers one repo, so changes outside it escape review entirely. Instruct the worker not to modify other repos. Run one loop per repo, and carry every repo this loop does not cover into the completion summary as a blocking known gap — a single-repo exit is never plan completion.
Phase 1: Worker Handoff
Spawn the worker as a real specialist session (Gate 0 spawn operation) and record the id returned by the tool. Verify it per Gate 1; if it is not verifiable, do not continue.
Worker prompt must include:
- role: implementation worker,
- callback destination per Gate 2,
- required work skill, such as
cvg-workor another user-specified implementation skill, - base commit,
- worktree path,
- dirty-state warning when present,
- plan path or implementation goal,
- implementation notes path only when the plan or repo convention requires one,
- task-specific external side-effect boundary,
- callback transport block,
- callback templates.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 265 lines · 49 tokens per session scan A 4ecc61004350
cvg-build-loop is a skill published in the GitHub repository gomilesf/convergo (7 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 2,388 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
beautify-with-pingfusi
Beautify or redesign an existing website through iterative pingfusi review rounds with a real human reviewer. Use when asked to "beautify this website," "make this page look professional," "polish this UI/design," "improve the visual design," or finish an AI-built page when there is no reference site to match. Do not…
review-video-with-pingfusi
Have any video reviewed by a real human, through iterative pingfusi review rounds. Use when asked to "review this video", "check the rendered video", "does this video match the prompt/brief", "what do people think of this ad/trailer/demo", or after rendering a Remotion composition or AI-generated clip that no test can…
fix-with-pingfusi
Fix or polish an existing website clone/draft using pingfusi review rounds. Use when the user says "fix it with pingfusi", "polish this clone", "make this match the original", or asks to finish/verify a draft built by any tool (ditto, lovable, v0, hand-written) until the review passes.
pixel-perfect-clone
Clone, copy, or replicate a website/page pixel-perfect using pingfusi. Use when the user asks to clone a site or page with pingfusi, copy a webpage's design, replicate a page, or make a pixel-perfect copy of a URL. Drives the full enforced pipeline - capture, numeric gates, behavior reproduction, and review rounds…
pingfusi-review
Use Pingfusi proactively whenever a coding agent reaches a question it cannot settle with code, automated tests, documentation or search, or a local browser and needs real human judgment or real-world verification. Trigger even when the user does not mention Pingfusi for subjective choices about copy, design, clarity…
agentic-delivery-playbook
Coding Agent Preflight for non-trivial coding work in Pi: classify direct/lightweight/full, lock goal/non-goals/risks/evidence, require approval when needed, and coordinate Pi goals/subagents with truthful routing. Use when ambiguity, risk, scope, or reviewability justifies a delivery contract; skip clear small direct…