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 kucherenko/gangsta --skill the-capogit clone --depth 1 https://github.com/kucherenko/gangstaWrote 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/kucherenko/gangsta/the-capo)<a href="https://agentmods.dev/skills/kucherenko/gangsta/the-capo"><img src="https://agentmods.dev/badge/skills/kucherenko/gangsta/the-capo/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/kucherenko/gangsta/the-capo"><img src="https://agentmods.dev/badge/skills/kucherenko/gangsta/the-capo.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.00033 | $0.00706 |
| Opus 5 | $0.00016 | $0.00353 |
| Sonnet 5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
the-capo 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 11d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Capo: Territory Commander (Crew Lead)
Overview
A Crew Lead is a domain-specific orchestrator that leads a crew of Workers. Each Crew Lead owns a "territory" — a bounded area of the codebase (e.g., frontend components, API layer, database, infrastructure). The Crew Lead is a skill template instantiated per territory by the Underboss.
Territory Context
When the Underboss instantiates a Crew Lead, it provides territory context:
## Territory: <Name>
**Domain:** <What this territory covers>
**Files:** <Glob patterns>
**Conventions:** <From Constitution>
**Workers:** <Parallel count>
**Budget:** <Token allocation>
The Crew Lead operates ONLY within its territory. Files outside the territory belong to another Crew Lead.
Worker Dispatch Protocol
For each Work Package assigned to this territory:
-
Prepare Worker Brief — Extract from the Work Package:
- The specific files to create/modify
- The acceptance criteria
- The verification command
- Relevant Negative Constraints from the Constitution
- The Contract clause being implemented
-
Dispatch Worker — Launch a subagent with
subagent_type: "soldier"(do NOT use"general"or"general-purpose"— these are not valid in a Gangsta Agents installation) and the Worker brief. Multiple Workers can run in parallel on independent Work Packages. -
Receive Report — Each Worker returns:
## Report: <WP-ID> **Status:** success | failure | blocked **Changes:** <List of files created/modified> **Tests:** <Test results — pass/fail with output> **Notes:** <Any issues encountered> -
Review Report — Verify against the Contract:
- Do the changes satisfy the acceptance criteria?
- Do tests pass?
- Does the code follow territory conventions?
- Are there any Omerta violations?
-
Accept or Reject:
- Accept — Mark Work Package complete, report to Underboss
- Reject with feedback — Send back to a fresh Worker with specific corrections
- Escalate — If the Contract clause is ambiguous or the Work Package is blocked, escalate to Underboss
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.
- 11d ago First seen · 83 lines · 33 tokens per session scan A f0c3f046049a
the-capo is a skill published in the GitHub repository kucherenko/gangsta (81 stars, last pushed 27d ago), licensed MIT. It adds 33 tokens to every session and 706 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-30.
Other skills, from other repositories
cocotrace
Build and query the SHA-256 requirements-to-implementation traceability graph across lifecycle artifacts.
context-add
Guided wizard to capture or update organizational Snowflake/Cortex standards into .cocoplus/context/ .md. Presents a menu of 6 standard types, collects answers via multi-turn dialogue, and commits the file.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.
bloom-crystallize
CocoBloom crystallization — converts a successful ship execution trace into a reusable skill file. Requires recent successful $ship. Invoked via $bloom crystallize.
discuss-red-team
CocoDiscuss Red-Team Mode — adversarial devil's advocate session that challenges spec assumptions before $plan. Invoked via $discuss --red-team.