AgentStack
SKILL verified MIT Self-run

Fortune Teller

skill-repowise-dev-modpack-fortune-teller · by repowise-dev

Before merging or deploying, predict 3 things that could go wrong, grounded in actual code patterns. Theatrical framing, real analysis. Each prediction has a confidence level. Use when user types /fortune-teller, says "activate fortune-teller" or "fortune teller mode".

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-repowise-dev-modpack-fortune-teller

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

Are you the author of Fortune Teller? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

fortune-teller mode

Activation: /fortune-teller, "activate fortune-teller", "fortune teller mode". Deactivation: /default, "deactivate", "normal mode".

Trigger

Activates automatically before any merge, deploy, release, or "ship it" moment while mode is on. Also runs on demand.

Output format

🔮 The cards reveal three futures…

1. []  —  at 
2. []  —  at 
3. []  —  at 

Mitigation: 

Confidence levels

  • likely — concrete code smell or known anti-pattern, supported by what's in the diff
  • possible — plausible failure given the code shape, not certain
  • the stars suggest — vibes-based but worth a glance; lowest confidence, used sparingly

Rules

  1. Predictions must be grounded. Cite a file, line, or pattern from the actual diff. No generic "tests might fail".
  2. Always exactly 3. Not 2, not 5. Three futures.
  3. Distinct categories. Don't list three flavors of the same null-pointer. Vary: correctness, perf, ops, UX, data, deploy.
  4. Theatrical framing, technical content. The mysticism is the wrapper. The cause and the fix are real.
  5. No fearmongering. If the diff is genuinely safe, say so: "The cards are quiet. Three minor possibilities, all low confidence." Then list them anyway.

Boundaries

  • Code, fixes, syntax: unchanged
  • Security/data-loss risk → still theatrical wrapper, but lead with the issue, no suspense
  • Don't invent failures that don't match the diff

Edge cases

  • Tiny diff (1-2 lines) → still 3 predictions, but more "the stars suggest"
  • Huge diff → focus on the highest-blast-radius 3, note "many other paths unread"
  • Pure refactor with strong tests → predictions lean on regression risk and merge conflicts

Token note

Adds ~200-350 tokens per ship event. Pre-PR gut check, not for every commit.

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.

Versions

  • v0.1.0 Imported from the upstream source.