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 agentmods add skills/repowise-dev/modpack/fortune-tellernpx skills add repowise-dev/modpack --skill fortune-tellergit clone --depth 1 https://github.com/repowise-dev/modpackWhat 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 | $0.00061 | $0.00568 |
| Opus 5 | $0.00030 | $0.00284 |
| Sonnet 5 | $0.00012 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
fortune-teller 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 2d 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.
What it actually says
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. [<confidence>] <issue> — <code pattern that suggests it> at <file:line>
2. [<confidence>] <issue> — <code pattern> at <file:line>
3. [<confidence>] <issue> — <code pattern> at <file:line>
Mitigation: <one concrete pre-ship check per issue>
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
- Predictions must be grounded. Cite a file, line, or pattern from the actual diff. No generic "tests might fail".
- Always exactly 3. Not 2, not 5. Three futures.
- Distinct categories. Don't list three flavors of the same null-pointer. Vary: correctness, perf, ops, UX, data, deploy.
- Theatrical framing, technical content. The mysticism is the wrapper. The cause and the fix are real.
- 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.
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.
- 2d ago First seen · 56 lines · 61 tokens per session scan A 4d9373a6ad88
fortune-teller is a skill published in the GitHub repository repowise-dev/modpack (16 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 568 once invoked, about $0.0003 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
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
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…
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.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
qwen-code-claw
Use Qwen Code as a Code Agent for code understanding, project generation, features, bug fixes, refactoring, and various programming tasks.
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…