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 skills add gomilesf/convergo --skill cvg-multi-sessiongit 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-multi-session)<a href="https://agentmods.dev/skills/gomilesf/convergo/cvg-multi-session"><img src="https://agentmods.dev/badge/skills/gomilesf/convergo/cvg-multi-session/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/gomilesf/convergo/cvg-multi-session"><img src="https://agentmods.dev/badge/skills/gomilesf/convergo/cvg-multi-session.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.00054 | $0.02700 |
| Opus 5.5 | $0.00022 | $0.01080 |
| Sonnet 5.5 | $0.00011 | $0.00540 |
| Haiku 4.5 | $0.00005 | $0.00270 |
Grade A, and why
cvg-multi-session 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 1mo 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Session Workflow
Use this skill when the current session should act as an orchestrator over other real specialist sessions.
The workflow is repo-independent. Specialist prompts should carry only the coordination data the specialist cannot infer from the selected role skill and source artifact. Do not paste broad repo rules, likely-file lists, old phase state, or role-skill procedures unless they are task-specific authority.
Non-Negotiable Protocol Gates
Apply these gates before any planner, worker, reviewer, QA runner, or quality reviewer is launched.
Gate 0: Transport Binding
Tool contracts and existing user authorization govern task creation, delegation and external actions; a skill invocation does not grant additional permissions.
Bind the specialist operations to the current platform before applying any other gate:
| Operation | Codex | Claude Code |
|---|---|---|
| Spawn specialist | create_thread |
Agent tool with run_in_background: true |
| Continue specialist | send_message_to_thread on the same thread id |
SendMessage to the agent id |
| Verify identity | read_thread on the returned thread id |
agent id in the Agent tool result |
| Inspect output | wait_threads and read_thread |
TaskOutput or the completion notification |
| Wait | one bounded wait_threads call, then heartbeat handoff if still active |
end the turn; the harness re-invokes the orchestrator on <task-notification> |
The authoritative specialist identity is always the id returned by the platform tool — never an id the specialist writes in prose. Do not accept placeholder specialist identity in callback templates.
On Claude Code, background specialists can spawn their own subagents (auxiliary
reviewers, researchers), and a completed specialist is resumed from its
persisted transcript when continued with SendMessage. Both loop requirements
are natively supported; do not flatten a specialist's internal delegation into
the orchestrator.
If the transport tools are not available after searching for them, report a tool-layer blocker. Do not fall back to inline simulation of a specialist.
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.
- 1mo ago Changed · +1 lines 4b69be311360
- 1mo ago First seen · 248 lines · 54 tokens per session scan A 63cf9559ff03
cvg-multi-session is a skill published in the GitHub repository gomilesf/convergo (8 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 2,700 once invoked, about $0.0002 per session on Opus 5.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…
architecture-review
Method for assessing a codebase's structure — duplication, single-responsibility violations, layering problems, and coupling — and recommending minimal, incremental improvements. Use when asked to review architecture, assess structure or technical debt, evaluate module boundaries, or plan a refactor. Reviews the…