one-way-door

one-way-door is a skill for Claude Code, Codex from jamditis/claude-skills-journalism. It costs 29 tokens per session (1,865 once invoked), scanned A, original, MIT.

A review for software decisions that become difficult or expensive to change after other code, users, or systems depend on them. These include database schemas, authentication boundaries, API contracts, event formats, and deployment pipelines.

In plain words
What is it for?
Use it when designing data models, infrastructure, authentication, APIs, event schemas, or CI/CD systems. It prompts questions about relationships, compatibility, permissions, and future changes.
Why use it?
It helps expose long-term risks before committing to an architectural choice that may require costly migrations or break dependent systems.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Part of the dev-toolkit plugin — 14 skills shipped together

Good fit Use it when designing data models, infrastructure, authentication, APIs, event schemas, or CI/CD systems. It prompts questions about relationships, compatibility, permissions, and future changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jamditis/claude-skills-journalism/one-way-door
Install

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.

Any agent
npx skills add jamditis/claude-skills-journalism --skill one-way-door
Clone the repo
git clone --depth 1 https://github.com/jamditis/claude-skills-journalism

Made for: Claude Code, Codex.

Or install dev-toolkit, the plugin that ships this one along with the rest of its 14 skills.

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

agentmods badge for one-way-door

README.md
[![agentmods](https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/one-way-door/github.svg)](https://agentmods.dev/skills/jamditis/claude-skills-journalism/one-way-door)
Your own site
<a href="https://agentmods.dev/skills/jamditis/claude-skills-journalism/one-way-door"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/one-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.

agentmods 80×15 button for one-way-door

Your own site · 80×15
<a href="https://agentmods.dev/skills/jamditis/claude-skills-journalism/one-way-door"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/one-way-door.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,865 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 145
    Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
    Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
  • medium Rogue Agent · line 361
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01865
Opus 5.5 $0.00012 $0.00746
Sonnet 5.5 $0.00006 $0.00373
Haiku 4.5 $0.00003 $0.00186

Measured 3d ago against content hash a5425fe8a98e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

one-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 3d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (one-way-door-approve.ps1, one-way-door-check.ps1), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

dev-toolkit/skills/one-way-door/SKILL.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

One-way door check

Some decisions are easy to reverse, you can change a UI component, rename a variable, or swap a utility function with no lasting consequences. These are two-way doors: walk through, and if it's wrong, walk back.

Other decisions create gravity. Once traffic, users, or other code depends on them, changing course gets expensive. A database schema migration after launch. An API contract that external consumers rely on. An auth boundary that shapes your entire permission model. These are one-way doors.

The most expensive mistakes in software aren't bugs. They're irreversible architectural decisions made too quickly.

What gets flagged

Data models and database schemas

Files matching: schema.prisma, schema.graphql, *.sql, migration*, models.py, models.ts, entities.py, entities.ts

Data models are the hardest decisions to reverse. Once your database has rows, every schema change requires a migration. Column renames break queries. Relationship changes cascade through your entire application.

Questions to ask:

  • Have you mapped all the relationships between entities?
  • Will this schema support the queries you need without N+1 problems?
  • Are you normalizing appropriately for your read/write patterns?

Infrastructure and deployment configs

Files matching: docker-compose*, Dockerfile, *.tf, terraform*, pulumi*, cdk*, cloudformation*, k8s*, kubernetes*, helm*

Infrastructure choices constrain everything built on top of them. Switching from ECS to Kubernetes, or from Lambda to containers, affects deployment pipelines, monitoring, scaling, and team knowledge.

Questions to ask:

  • Is this the simplest infrastructure that meets your needs?
  • What's your team's operational experience with this stack?
  • What does failure recovery look like?

Authentication and authorization

Files matching: auth.{ts,js,py}, firestore.rules, storage.rules, *.rules, security.{ts,js,py,json,rules,yaml,yml}, rbac.{ts,js,py,json}, permissions.{ts,js,py,json}

Read the full file on GitHub · 181 lines

Files

What ships with it

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

Changes

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.

  1. 3d ago Changed · -242 lines a5425fe8a98e
  2. 1mo ago First seen · 423 lines · 29 tokens per session scan A c019ad81e7ed

Subscribe to this mod's changes

one-way-door is a skill published in the GitHub repository jamditis/claude-skills-journalism (437 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 1,865 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

audit-engine

Activate when the user wants to audit a paper's empirical or technical claims against a linked code repository — checking whether experiments, datasets, models, metrics, and hyperparameters described in the paper actually exist and match the code. Produces a structured audit report classifying each claim as CONFIRMED…

TobiasBlask/open-paper-machine · 109 tokens

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

code-yeongyu/oh-my-openagent · 63 tokens

pr-summary

Refresh the current pull request description from its net changes, following the repository's PR template, when asked to update or write the PR summary. Works in any Scenario repository, whatever its default branch.

scenario-labs/skills · 42 tokens

refactor-advisor

A code review helper that finds common design and maintenance problems in a codebase and suggests ways to restructure the code.

laolaoshiren/claude-code-skills-zh · 22 tokens

r-tidyverse-style

Use when the user asks to review or clean up R code for tidyverse style, standardize formatting or names, remove redundant comments or wrappers, or make a behavior-preserving style pass. Also use when writing substantial new R package code if the user requests tidyverse style or the package already follows it. Not for…

posit-dev/skills · 83 tokens

techdebt

Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.

oliver-kriska/claude-elixir-phoenix · 36 tokens