Borrowing it
Nothing to install: this file belongs to termio-sh/termio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/termio-sh/termio/main/CLAUDE.mdgit clone --depth 1 https://github.com/termio-sh/termioWrote 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/instructions/termio-sh/termio/claude-md)<a href="https://agentmods.dev/instructions/termio-sh/termio/claude-md"><img src="https://agentmods.dev/badge/instructions/termio-sh/termio/claude-md/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/instructions/termio-sh/termio/claude-md"><img src="https://agentmods.dev/badge/instructions/termio-sh/termio/claude-md.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.00803 | $0.00803 |
| Opus 5.5 | $0.00321 | $0.00321 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
termio CLAUDE.md 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 today.
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.
@AGENTS.md
termio
What termio is
A terminal-first agentic development environment, including its own remote server.
Coding agents live in terminals. termio is the place those agents run, on machines
the user already owns — a laptop, a VPS, a devbox — supervised from a native Mac
app and an iPhone. termiod is the durable session host that makes "on any box"
one code path instead of four.
The category is crowded (Zed remote, VS Code Remote, Codespaces, Warp). That is a known and accepted cost of this position, not an oversight. Do not re-argue the positioning. Build it.
What makes it different (aim here, not at editors)
- The session lives on the box, not in the connection. Detach ≠ kill. An agent keeps working while the laptop is shut; reattach restores the exact screen. Zed and VS Code tie remote work to a live connection; termio does not.
- The user's machines, not our cloud. termio never provisions compute and never runs a hosted control plane. The code never leaves hardware the user controls — the only trust story that survives giving an agent shell access to a private repo.
- Agent-native at the protocol level. Workstream status (
working/idle/needs-you/done) is a first-class protocol object, not a heuristic scraped off the screen. - Terminal-first is a commitment, not a stage. The terminal is the interface. Chat UIs have been built and fully reverted twice. Don't rebuild them.
Architectural non-negotiables
These come from docs/design/20260730-termiod-session-protocol.md §A and §H. Violating one
is a design regression, not a tradeoff:
- Anti-100× invariant — byte delivery never blocks on host-side VT parse. The authoritative VT is a sidecar for snapshots; any per-frame grid encoder between the PTY and the pipe rebuilds the tmux tax and is rejected.
- State sync only at boundaries — snapshots on attach / resize / resync, never
per frame.
grid_diffis an opt-in bad-network degrade, never the default. - Never embed SSH or crypto. System OpenSSH, tailnets, and OS keychains are the
security team we didn't hire. The user's
~/.ssh/configis authoritative — read it, never override it. One exception, chosen on purpose: built-in Tailscale. Tailscale's own tsnet library runs intermio-tailnet(termiod/tailnet), a separate helper process, never linked into termiod or the app. Nothing else brings its own crypto. - One protocol, versioned and transport-agnostic. Unix socket, SSH stdio, and later QUIC carry the same framed messages. No second protocol for the phone.
- Layout lives in termiod as control-plane state. One PTY per session. The
host owns projects, groups, panes, focus and zoom; clients keep only their
viewport. Nothing about layout runs on the byte path. See
docs/design/20261025-termiod-owns-the-view.md. - Single writer, many readers. Observers never claim the write token.
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.
- today Changed · +2 lines · +43 tokens per session 35c9de65bee5
- 2d ago Changed · +3 lines · +63 tokens per session 4dded7da65a4
- 1mo ago First seen · 57 lines · 697 tokens per session scan A 00f1c592fd63
termio CLAUDE.md is an instructions file published in the GitHub repository termio-sh/termio (638 stars, last pushed today), licensed MIT. It adds 803 tokens to every session, about $0.0032 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.