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 product-on-purpose/thinking-framework-skills --skill think-futures-wheelgit clone --depth 1 https://github.com/product-on-purpose/thinking-framework-skillsWrote 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/product-on-purpose/thinking-framework-skills/think-futures-wheel)<a href="https://agentmods.dev/skills/product-on-purpose/thinking-framework-skills/think-futures-wheel"><img src="https://agentmods.dev/badge/skills/product-on-purpose/thinking-framework-skills/think-futures-wheel/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/product-on-purpose/thinking-framework-skills/think-futures-wheel"><img src="https://agentmods.dev/badge/skills/product-on-purpose/thinking-framework-skills/think-futures-wheel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00070 | $0.00791 |
| Opus 5 | $0.00035 | $0.00396 |
| Sonnet 5 | $0.00014 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
think-futures-wheel 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 12d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Futures Wheel
Most analysis stops at first-order consequences: the immediate, obvious results. A futures wheel pushes past that. The change goes at the center; first-order consequences radiate around it; each of those spawns second-order consequences ("and then what?"); then third-order. The structure forces attention onto the downstream and cross-domain ripples that linear thinking skips, and flags the branches worth a response. The output is a consequence map. For a quick pass, a lightweight "second-order effects" mode runs only the first-to-second step.
When to Use
- A decision or change has knock-on effects that play out over time.
- First-order analysis is missing downstream risks or opportunities.
- Scanning the systemic side effects of a new idea before committing.
When NOT to Use
- Simple, linear situations with no meaningful higher-order effects.
- When you need to decide, not explore (hand the map to a decision skill).
- When the result would be branches to irrelevance rather than a focused map.
Instructions
When asked to build a futures wheel, follow these steps:
- Center it. State the change or decision at the middle, in one line.
- First order. List the immediate, direct consequences. Span domains (technical, financial, customer, team, competitive), not just the obvious one.
- Second order. For each meaningful first-order effect, ask "and then what happens?" and add its consequences.
- Third order. For the branches that still matter, extend one more step. Stop a branch when it goes trivial.
- Flag the branches that matter. Mark the high-impact or non-obvious consequences, and add a one-line "watch or do about it" for each.
- Emit the consequence map per
references/TEMPLATE.md.
Output Format
Use the template in references/TEMPLATE.md. The deliverable is the nested consequence map with flagged branches, not prose.
What ships with it
6 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.
- 12d ago First seen · 62 lines · 70 tokens per session scan A e075588c4961
think-futures-wheel is a skill published in the GitHub repository product-on-purpose/thinking-framework-skills (15 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 791 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
ops-demo
CocoOps demo mode activator — populates .cocoplus/ops/demo/ with realistic mock data and sets cocoplus.toml [demo] enabled = true. Invoked via $ops demo.
acl-rule-analysis
Vendor-agnostic ACL and firewall rule analysis with shadowed rule detection, overly permissive rule identification, unused rule discovery, redundant rule flagging, and rule ordering optimization. Covers ACLs (Cisco/JunOS/EOS) and firewall policies (PAN-OS/FortiGate/CheckPoint).
add-analytics
Add Google Analytics 4 tracking to any project. Detects framework, adds tracking code, sets up events, and configures privacy settings.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…
agent-team-orchestration
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4)…
agent-bom-enforce
Enforce security policies on MCP tool calls and block dangerous operations at runtime. Use when: "block risky calls", "apply policy", "proxy", "runtime protection", "policy enforcement", "intercept MCP calls".