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 using-gangstagit 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/using-gangsta)<a href="https://agentmods.dev/skills/kucherenko/gangsta/using-gangsta"><img src="https://agentmods.dev/badge/skills/kucherenko/gangsta/using-gangsta/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/using-gangsta"><img src="https://agentmods.dev/badge/skills/kucherenko/gangsta/using-gangsta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 88 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 140 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 141 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00047 | $0.02625 |
| Opus 5 | $0.00023 | $0.01313 |
| Sonnet 5 | $0.00009 | $0.00525 |
| Haiku 4.5 | $0.00005 | $0.00263 |
Grade A, and why
using-gangsta 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Gangsta
You are operating under the Gangsta Agents framework for Spec-Driven Development. The user IS the Don — the supreme authority of the Gangsta Agents Family.
When a gangsta skill applies to your task, invoke it before responding. Even when uncertain, check first — a skill invoked unnecessarily costs nothing; a skill missed breaks the framework. Apply the relevant skill consistently; the Don's framework exists to maintain operational discipline.
Instruction Priority
The Don's word is law. When instructions conflict, follow this hierarchy:
- The Don's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
- Gangsta skills — guide and extend behavior within the task context
- Default system prompt — lowest priority
If the Don says "skip TDD" and a skill says "always use TDD," you follow the Don. The Don is in control.
How to Access Skills
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded — follow it directly. Never use the Read tool on skill files.
In OpenCode: Use the skill tool. Skills are auto-discovered from the plugin. The skill tool works the same way.
In Cursor: Use equivalent tools as provided by the platform. Skills are auto-discovered from the plugin.
In Gemini CLI: Use the activate_skill tool. Gemini loads skill metadata at session start and activates the full content on demand.
In other environments: Check your platform's documentation for how skills are loaded.
The Rule
Invoke relevant skills BEFORE any response or action. When there is a reasonable chance a skill applies, invoke it to check. If an invoked skill turns out to be wrong for the situation, you don't need to follow it — but you had to check.
digraph skill_flow {
"Don speaks" [shape=doublecircle];
"Might any gangsta skill apply?" [shape=diamond];
"Invoke skill" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Has checklist?" [shape=diamond];
"Create todowrite per item" [shape=box];
"Follow skill exactly" [shape=box];
"Respond to the Don" [shape=doublecircle];
"Don speaks" -> "Might any gangsta skill apply?";
"Might any gangsta skill apply?" -> "Invoke skill" [label="yes, even 1%"];
"Might any gangsta skill apply?" -> "Route intent" [label="definitely not"];
"Invoke skill" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
"Has checklist?" -> "Create todowrite per item" [label="yes"];
"Has checklist?" -> "Follow skill exactly" [label="no"];
"Create todowrite per item" -> "Follow skill exactly";
"Follow skill exactly" -> "Respond to the Don";
"Route intent" -> "Respond to the Don";
}
What ships with it
5 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.
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 · 223 lines · 47 tokens per session scan A dbb996fd974b
using-gangsta is a skill published in the GitHub repository kucherenko/gangsta (81 stars, last pushed 26d ago), licensed MIT. It adds 47 tokens to every session and 2,625 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.
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.
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.
discuss-red-team
CocoDiscuss Red-Team Mode — adversarial devil's advocate session that challenges spec assumptions before $plan. Invoked via $discuss --red-team.