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-one-way-vs-two-way-doorgit 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-one-way-vs-two-way-door)<a href="https://agentmods.dev/skills/product-on-purpose/thinking-framework-skills/think-one-way-vs-two-way-door"><img src="https://agentmods.dev/badge/skills/product-on-purpose/thinking-framework-skills/think-one-way-vs-two-way-door/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-one-way-vs-two-way-door"><img src="https://agentmods.dev/badge/skills/product-on-purpose/thinking-framework-skills/think-one-way-vs-two-way-door.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.00119 | $0.01355 |
| Opus 5 | $0.00060 | $0.00678 |
| Sonnet 5 | $0.00024 | $0.00271 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
think-one-way-vs-two-way-door 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One-Way vs Two-Way Door
This is a meta-decision tool: a triage that runs before any option comparison and asks one question - how reversible is this decision? - then matches the deliberation and sign-off to the answer. A two-way door is reversible (walk back cheaply), so decide it fast, low, and light. A one-way door is hard or expensive to reverse, so give it real rigor and senior sign-off. The load-bearing move is separating the reversibility judgment from the decision itself, which routes scarce deliberation toward the irreversible few and licenses speed on the reversible many. The output is a reversibility classification plus a matched deliberation level - it says how much machinery the choice deserves, never which option to pick.
When to Use
- A decision is on the table and it is unclear how much process it deserves.
- Someone is about to rubber-stamp something irreversible, or convene a committee over something trivially reversible.
- A team or org is chronically slow, applying the same heavyweight approval to everything regardless of stakes.
- You want an explicit, defensible reason - decided before deliberation starts - to either move fast or slow down.
When NOT to Use
- When the decision is already known to be high-stakes and is being analyzed. Triage already happened; you are past this tool. Use a risk tool (premortem) or an option comparison, not a classifier that confirms what you know.
- When you need to actually compare options against criteria. That is
think-decision-option-review(a criteria-weighted option matrix). This skill triages before any comparison how much analysis the decision warrants; it never scores or recommends an option. - As a license for speed alone. If the irreversible-but-inconvenient consequences (trust, legal, path-dependence) get waved away, the classification is motivated, not honest.
- As theater to bless a fast decision by labeling a one-way door a two-way door. The verdict has to be defensible.
- For a routine, obviously reversible call with no meaningful reversibility question. Just decide; classifying it is its own small over-process.
What ships with it
5 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 · 64 lines · 119 tokens per session scan A 0a72ce201667
think-one-way-vs-two-way-door 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 119 tokens to every session and 1,355 once invoked, about $0.0006 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".