Vibe-Skills is a collection and routing system that helps AI agents discover, select, and coordinate specialized skills for completing tasks. It is intended for agents that need to organize workflows across many installed capabilities. The catalogue entries are skills and an agent belonging to this system.
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 foryourhealth111-pixel/Vibe-Skills --skill local-vco-rolesgit clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-SkillsWrote 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/foryourhealth111-pixel/vibe-skills/local-vco-roles)<a href="https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/local-vco-roles"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/local-vco-roles/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/foryourhealth111-pixel/vibe-skills/local-vco-roles"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/local-vco-roles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00457 |
| Opus 5 | $0.00014 | $0.00229 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
local-vco-roles 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.
What it actually says
local-vco-roles
Codex-local role pack for dialectic multi-agent reviews, designed to be compatible with the local vibe skill.
When to Use
Use this skill when:
- You run
/vibeand need a stable role set for dialectic review. - You want reproducible multi-role analysis using TeamCreate-style orchestration.
- You need standardized outputs across team-lead / bug / architecture / integration / usability roles.
Vibe Compatibility Contract (Must Follow)
- Grade handshake:
- M/L: do NOT force TeamCreate orchestration.
- XL: TeamCreate workflow is allowed.
- Rule-1 boundary:
- Never mix multiple agent systems for the same task.
- Follow
vibeconflict rules first.
- Command priority:
- User explicit command >
viberouting > this role pack defaults.
- Output severity:
- Always use
CRITICAL > HIGH > MEDIUM > LOW.
- Staged confirmation:
- Keep major confirmation points aligned with
vibeteam protocol.
- Memory behavior:
- Default state tracking via TodoWrite-style task state.
- Optional enhancements (if available) must not become hard dependencies.
Role Prompt Library
- Team lead:
references/role-prompts/team-lead.md - Bug analyst:
references/role-prompts/bug-analyst.md - Architecture critic:
references/role-prompts/arch-critic.md - Integration analyst:
references/role-prompts/integration-analyst.md - Usability analyst:
references/role-prompts/usability-analyst.md
Recommended XL Workflow
- Read
references/vibe-compatibility.md. - Create 5 tasks (lead + 4 analysts).
- Assign each role using the prompt files above.
- Collect results and aggregate by severity.
- Produce one merged decision set (
keep / simplify / remove).
Optional Utility
- Run scaffold helper:
scripts/new-run.ps1 -Topic <name>
What ships with it
7 files 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.
- references/role-prompts/arch-critic.md 401 B
- references/role-prompts/bug-analyst.md 423 B
- references/role-prompts/integration-analyst.md 420 B
- references/role-prompts/team-lead.md 460 B
- references/role-prompts/usability-analyst.md 379 B
- references/vibe-compatibility.md 1.2 KB
- scripts/new-run.ps1 903 B runs code
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 · 60 lines · 28 tokens per session scan A 92e24c863bf4
local-vco-roles is a skill published in the GitHub repository foryourhealth111-pixel/Vibe-Skills (3,252 stars, last pushed 12d ago), licensed Apache-2.0. It adds 28 tokens to every session and 457 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-09-03.
Other skills, from other repositories
meta-reviewing-ai-reviewing
AI integration review patterns. Use when reviewing model API calls, prompt construction, LLM output handling, RAG pipelines, and tool-calling code. Covers prompt-injection call-chain tracing, output validation, token budgets, retry/timeout handling, streaming, and key/PII exposure.
meta-reviewing-api-reviewing
Backend code review patterns. Use when reviewing API routes, database operations, auth middleware, and server utilities. Covers injection, boundary validation, authorization coverage, secret/PII exposure, error leakage, and query patterns.
meta-reviewing-cli-reviewing
CLI code review patterns. Use when reviewing CLI applications built with Commander.js, @clack/prompts, picocolors. Covers exit codes, signal handling, error messages, user experience, testing adequacy.
meta-reviewing-infra-reviewing
Infrastructure code review patterns. Use when reviewing CI/CD workflows, Dockerfiles, deployment configs, and IaC. Covers supply-chain pinning, secret exposure, container hygiene, least-privilege permissions, and deployment safety.
meta-reviewing-web-reviewing
UI component review patterns. Use when reviewing React components, hooks, props, state, styling, and accessibility. Covers rules of hooks, effect cleanup, render performance, list keys, keyboard and ARIA patterns.
meta-reviewing-reviewing
Code review patterns, feedback principles. Use when reviewing PRs, implementations, or making approval/rejection decisions. Covers self-correction, progress tracking, feedback principles, severity levels.