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 mshadmanrahman/pm-pilot --skill cruciblegit clone --depth 1 https://github.com/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/crucible)<a href="https://agentmods.dev/skills/mshadmanrahman/pm-pilot/crucible"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/crucible/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/mshadmanrahman/pm-pilot/crucible"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/crucible.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.00114 | $0.03952 |
| Opus 5 | $0.00057 | $0.01976 |
| Sonnet 5 | $0.00023 | $0.00790 |
| Haiku 4.5 | $0.00011 | $0.00395 |
Grade A, and why
crucible 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 4d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crucible
A council of specialized personas debates one idea under structured conflict. The chair synthesizes into a verdict. Transcripts are saved to disk for second-brain reuse.
Use this when the cost of being wrong is high enough to justify convening 5-10 subagents. For one-lens exploration without a debate, use Solo mode. For tactical questions under five minutes of normal thinking, don't use Crucible at all.
When to trigger
Trigger on explicit user invocation only. Examples:
/crucible <idea>(Decision mode default)/crucible --council <idea>or/crucible --quick <idea>(Council mode)/crucible --pm <idea>(PM Daily mode)/crucible --solo <persona> <idea>or natural language ("give me the First Principles read on X")/crucible --existential <idea>- "Run this through the crucible: ..."
- "Convene the crucible on ..."
Do not auto-trigger. This is an expensive skill and the user decides when it runs.
Five modes
The chair selects mode at intake based on the user's phrasing OR an explicit flag. Most daily use belongs in Council or Solo. Decision and Existential are for real decisions with real stakes.
Mode 1: Solo (single-persona lens, ~10-15 seconds)
Triggers: /crucible --solo <persona>, or natural language ("give me the First Principles read on X", "what does the Expansionist think about Y", "Track Record this for me").
Persona count: 1. No duels. No chair verdict. The chair's only job is persona-matching and returning the rubric output unchanged.
Use for: Exploration, not decisions. When you want one specific lens, not a debate.
Honesty check: If you find yourself reaching for Solo to avoid hearing the Contrarian, that's a signal to run Council mode instead.
Mode 2: Council (daily reflex, ~30-45 seconds)
Triggers: "council", "quick crucible", "gut check", "throw rocks at this", "poke holes", "sanity check", /crucible --council, /crucible --quick.
Bench: 5 personas, parallel openings only. No duels. No verdict beyond a one-liner.
- Contrarian (Sonnet, NOT Opus at this tier to keep cost down)
- First Principles (Sonnet at this tier)
- Expansionist (Sonnet)
- Outsider (Haiku)
- Operator (Haiku)
What ships with it
3 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.
- 4d ago Changed · +1 lines 68aa596c10e4
- 9d ago First seen · 238 lines · 114 tokens per session scan A f1dc51be41c0
crucible is a skill published in the GitHub repository mshadmanrahman/pm-pilot (20 stars, last pushed 3d ago), licensed MIT. It adds 114 tokens to every session and 3,952 once invoked, about $0.0006 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
build-implementation
Generate context-aware implementation prompts for a selected growth loop. Use when the user says "build", "implement", "generate code", "create prompt", or "how do I build this".
analyze-codebase
Run comprehensive PLG analysis on a codebase to detect tech stack, existing growth features, and revenue opportunities. Use when the user says "analyze", "scan", "audit codebase", or "find growth opportunities".
deploy-telemetry
Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics", "tracking", "events", "push to supabase", or "skene push".
plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".
validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
initialize-config
Set up Skene configuration for a project. Use when starting a new PLG analysis, when .skene.config is missing, or when the user says "skene init", "set up skene", or "configure skene".