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 ByJH/airlock --skill skillgit clone --depth 1 https://github.com/ByJH/airlockWrote 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/byjh/airlock/skill)<a href="https://agentmods.dev/skills/byjh/airlock/skill"><img src="https://agentmods.dev/badge/skills/byjh/airlock/skill/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/byjh/airlock/skill"><img src="https://agentmods.dev/badge/skills/byjh/airlock/skill.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.00036 | $0.00579 |
| Opus 5.5 | $0.00014 | $0.00232 |
| Sonnet 5.5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
airlock 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airlock
A gate for the things an agent installs. Use it before adding any skill, MCP server, or tool repo that came from a source you have not fully vetted. It works out what the artifact is, scans it for dangerous shapes, reads it adversarially with a model, detonates it once in a sealed sandbox, and returns one verdict.
When to run it
Run Airlock on an extension before the install step, not after. Good moments:
- Someone shares a
SKILL.mdfolder or a repo URL and asks you to install it. - You are about to add an MCP server you found in a public registry.
- A dependency wants to run a lifecycle hook on install.
How to run it
Airlock is a Python command line tool. Install it once, then point it at a path or a cloned repo:
pip install -e ".[sandbox]" # from the Airlock repo
airlock audit path/to/extension
The exit code is the gate, so a script or a hook can branch on it:
0allow. No known-bad shape, a clean or skipped judgment, no canary touch.1quarantine. Something needs a human to look before it goes in.2block. A critical finding, a canary touch, or a judged exfiltration.
Add --json for a machine-readable scorecard, --no-llm to run the
deterministic core with no API key, and --no-sandbox to skip the container
trial. The deterministic core always produces a verdict, even offline.
How to act on the verdict
- On block, do not install the extension. Read the cited findings and tell the user which line drove the decision.
- On quarantine, hold the install for a human review. Summarize what the scan and the judge flagged.
- On allow, it is safe to proceed. A clean scan means no known-bad shape matched, not a proof of safety, so still prefer trusted sources.
What it looks at
The scorecard lists every finding with a file and line: credential-file reads, environment exfiltration, reverse shells, remote installers that pipe a downloaded script into a shell, package lifecycle hooks, and prompt-injection phrasing aimed at the agent reading the skill. The final gate is deterministic, so the same artifact always grades the same way and a model is never the last word on what gets in.
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.
- 1mo ago First seen · 58 lines · 36 tokens per session scan A cb4bc69322cd
airlock is a skill published in the GitHub repository ByJH/airlock (0 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 579 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…