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 agentmods add instructions/m4xx101/cryptex-oss/claude-mdgit clone --depth 1 https://github.com/m4xx101/cryptex-ossWrote 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/m4xx101/cryptex-oss/claude-md)<a href="https://agentmods.dev/instructions/m4xx101/cryptex-oss/claude-md"><img src="https://agentmods.dev/badge/instructions/m4xx101/cryptex-oss/claude-md.svg" alt="Measured on agentmods" 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 | $0.03329 | $0.03329 |
| Opus 5 | $0.01665 | $0.01665 |
| Sonnet 5 | $0.00666 | $0.00666 |
| Haiku 4.5 | $0.00333 | $0.00333 |
Grade A, and why
cryptex-oss 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 5d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributor + AI-Assistant Guide
This file is read by AI coding assistants (Claude, Copilot, Cursor, etc.) so they follow the project's conventions. Humans contributing PRs should skim it once too.
What this repo is
Cryptex OSS is a SvelteKit 2 + Svelte 5 + shadcn-svelte static-site app for LLM red-teaming techniques. The deliverable is a single-page browser app, served as static files. There is no backend, no database, and no auth; every piece of state lives in localStorage. The app exposes 25 tool routes (10 technique workbenches under /transforms, /decode, etc., plus 15 red-team labs under /redteam/*).
A Python CLI (cryptex-cli, managed with uv) shells out to Node to execute the canonical transformers in src/transformers/, so there is one source of truth for transforms: both the SvelteKit app and the CLI import the same 159 transformer files.
The v2.0 milestone hardened every tool surface with a unified ToolShell template, typed CryptexError taxonomy, Web Worker offloading for inputs at or above 50 KB, a per-tool Vault drawer (309 bundled OSS-licensed seed items + custom-add), and a persistent searchable session history via the v2 store. See the v2.0 conventions section below before adding new surfaces.
Commands
Primary (SvelteKit app)
cd app && npm install # install deps
cd app && npm run dev # Vite dev server, http://localhost:5173
cd app && npm run check # svelte-kit sync + svelte-check (type-check)
cd app && npx vitest run # run all unit tests
cd app && npx vitest run path/to/file.test.ts # run a single test
cd app && npm run build # static build → app/build/
Python CLI (cryptex-cli)
uv run cryptex-cli list
uv run cryptex-cli inspect caesar --json
uv run cryptex-cli encode --transform base64 --text "Hello"
uv run cryptex-cli /base64 --decode SGVsbG8= # slash-command form
uv run cryptex-cli auto-decode --text "SGVsbG8="
pytest # python_tests/
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.
- 5d ago First seen · 211 lines · 3,329 tokens per session scan A 1966ad9773bd
cryptex-oss CLAUDE.md is an instructions file published in the GitHub repository m4xx101/cryptex-oss (338 stars, last pushed 2mo ago), licensed MIT. It adds 3,329 tokens to every session, about $0.0166 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 instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).