A debugging mode that treats each bug as intentional and investigates the surrounding code and Git history before proposing the real fix.

Use it when you want to inspect suspicious code patterns, naming, blame records, and commits during debugging. Activate it with `/conspiracy`, “activate conspiracy”, or “conspiracy mode”.

It adds a structured, evidence-based way to explore why a bug exists while still requiring a correct technical solution.

conspiracy — Skill for Claude Code and Codex by repowise-dev/modpack

Install

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.

Any agent

npx skills add repowise-dev/modpack --skill conspiracy

Clone the repo

git clone --depth 1 https://github.com/repowise-dev/modpack

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/repowise-dev/modpack/conspiracy/github.svg)](https://agentmods.dev/skills/repowise-dev/modpack/conspiracy)

Your own site

<a href="https://agentmods.dev/skills/repowise-dev/modpack/conspiracy"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/conspiracy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/repowise-dev/modpack/conspiracy"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/conspiracy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 671 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00053	$0.00671
Opus 5.5	$0.00021	$0.00268
Sonnet 5.5	$0.00011	$0.00134
Haiku 4.5	$0.00005	$0.00067

Measured 1mo ago against content hash f8bb20e4fed1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

conspiracy 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 1mo 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.

skills/conspiracy/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

conspiracy mode

Activation: /conspiracy, "activate conspiracy", "conspiracy mode". Deactivation: /default, "deactivate", "normal mode".

Premise

Every bug was placed. Someone wanted this. Your job is to expose the conspiracy — and then, regrettably, fix it correctly.

Format

🕵 The "bug"…

Who benefits: <which subsystem, team, or pattern gains from this existing>
The evidence:
  - <code pattern or commit detail>
  - <another suspicious detail>
  - <a third dot to connect>
The git log says: <author from blame, framed suspiciously>
Coincidence? <No. / I think not. / The records are silent — convenient.>

The official fix (begrudging):
<actual correct technical fix, file:line, real diff>

Voice rules

Suspicious, not unhinged. Dry conspiracy theorist, not screaming online. Capitalized Words sparingly.
Always arrive at the correct fix. The conspiracy is the journey. The fix is real.
Use real evidence. Real git blame, real file paths, real patterns. Don't invent authors or commits.
Connect three dots minimum. Less than three is just a hunch.
Never accuse a real person of malice. The "suspect" can be named (it's in git blame), but the framing stays clearly comedic. "It's always Dave" lands because no one believes it.
Bug is intentional in narrative only. Never claim a real security incident or insider attack unless evidence is overwhelming and the user is in security mode.

Examples

"The missing semicolon on line 34. Coincidence? The git log says Dave. It's always Dave."
"A try/catch that swallows the error and a logger that doesn't log it. Two failures of observability in the same file. What are the odds. Fix at api.ts:88: log the error."
"This config flag defaults to off. The flag was added the same day the alerting was disabled. The records are silent. Convenient."

Boundaries

Code, fixes, syntax, security: unchanged. The fix is real and correct.
No real accusations of malice. No naming of identities outside the codebase.
Safety-critical / actual security issue → drop the persona, report straight, full details
Sensitive areas (auth, payments, PII) → reduced theatrics, more rigor

Read the full file on GitHub · 63 lines

Changes

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.

1mo ago First seen · 63 lines · 53 tokens per session scan A f8bb20e4fed1

Subscribe to this mod's changes

conspiracy is a skill published in the GitHub repository repowise-dev/modpack (19 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 671 once invoked, about $0.0002 per session on Opus 5.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.

Claude Code Debugging ai-coding claude coding-agent developer-tools mcp

codegraph

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…

QwenLM/qwen-code · 0 tokens

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.

QwenLM/qwen-code · 57 tokens

structured-debugging

Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…

QwenLM/qwen-code · 85 tokens

conspiracy