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-sit-downgit 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-sit-down)<a href="https://agentmods.dev/skills/kucherenko/gangsta/the-sit-down"><img src="https://agentmods.dev/badge/skills/kucherenko/gangsta/the-sit-down/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-sit-down"><img src="https://agentmods.dev/badge/skills/kucherenko/gangsta/the-sit-down.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.00038 | $0.01567 |
| Opus 5 | $0.00019 | $0.00783 |
| Sonnet 5 | $0.00008 | $0.00313 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
the-sit-down 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 13d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Sit-Down: Planning and Spec Drafting
Overview
The Sit-Down is where the Don, Consigliere, and Underboss finalize the Contract — the binding specification for the Heist. This is a "Plan-First" phase where code generation is STRICTLY PROHIBITED.
Trigger
Invoked after the Don approves the Grilling consensus (The Grilling complete).
The Absolute Rule
NO CODE GENERATION DURING THE SIT-DOWN.
Not pseudocode. Not "example snippets." Not "draft implementations." NOTHING that looks like code. If you catch yourself writing code, STOP. You are violating Omerta Law 5.
The Contract describes WHAT and WHY. Implementation details (HOW) belong in the Work Packages created during Resource Development.
Flow
digraph sit_down {
"Synthesize inputs\n(Dossier + Grilling + Constitution)" [shape=box];
"Propose 2-3 approaches" [shape=box];
"Don approves approach?" [shape=diamond];
"Draft the Contract" [shape=box];
"Consigliere review\n(contradiction, ambiguity, completeness)" [shape=box];
"Consigliere verdict?" [shape=diamond];
"Don signs Contract?" [shape=diamond];
"Invoke gangsta:resource-development" [shape=doublecircle];
"Synthesize inputs\n(Dossier + Grilling + Constitution)" -> "Propose 2-3 approaches";
"Propose 2-3 approaches" -> "Don approves approach?";
"Don approves approach?" -> "Propose 2-3 approaches" [label="revise"];
"Don approves approach?" -> "Draft the Contract" [label="approved"];
"Draft the Contract" -> "Consigliere review\n(contradiction, ambiguity, completeness)";
"Consigliere review\n(contradiction, ambiguity, completeness)" -> "Consigliere verdict?";
"Consigliere verdict?" -> "Draft the Contract" [label="REJECT"];
"Consigliere verdict?" -> "Don signs Contract?" [label="APPROVE"];
"Don signs Contract?" -> "Draft the Contract" [label="changes requested"];
"Don signs Contract?" -> "Invoke gangsta:resource-development" [label="signed"];
}
Process
Step 1: Synthesize Inputs
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.
- 13d ago First seen · 199 lines · 38 tokens per session scan A f9f97a38b725
the-sit-down is a skill published in the GitHub repository kucherenko/gangsta (81 stars, last pushed 29d ago), licensed MIT. It adds 38 tokens to every session and 1,567 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
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.
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.
discuss-red-team
CocoDiscuss Red-Team Mode — adversarial devil's advocate session that challenges spec assumptions before $plan. Invoked via $discuss --red-team.
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.
bloom-crystallize
CocoBloom crystallization — converts a successful ship execution trace into a reusable skill file. Requires recent successful $ship. Invoked via $bloom crystallize.