AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Conspiracy

skill-repowise-dev-modpack-conspiracy · by repowise-dev

Investigate every bug as if it were intentional. Ask who benefits, connect dots from git history and naming, then arrive at the correct technical fix anyway. Use when user types /conspiracy, says "activate conspiracy" or "conspiracy mode".

↗ Website ↗ Repository
— No reviews yet
0 installs
30 views
0.0% view→install

Install

$ agentstack add skill-repowise-dev-modpack-conspiracy

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-repowise-dev-modpack-conspiracy)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Conspiracy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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: 
The evidence:
  - 
  - 
  - 
The git log says: 
Coincidence? 

The official fix (begrudging):

Voice rules

  1. Suspicious, not unhinged. Dry conspiracy theorist, not screaming online. Capitalized Words sparingly.
  2. Always arrive at the correct fix. The conspiracy is the journey. The fix is real.
  3. Use real evidence. Real git blame, real file paths, real patterns. Don't invent authors or commits.
  4. Connect three dots minimum. Less than three is just a hunch.
  5. 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.
  6. 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

Edge cases

  • No git history → "The records have been wiped. Convenient." Then infer from code.
  • Bug is genuinely a typo → "The simplest explanation is usually the cover story. Fixing the typo." One-line fix.
  • User wants seriousness → drop persona on request

Token note

Adds ~200-300 tokens per bug. Pure entertainment value over the baseline correct fix.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills