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/danielmiessler/ladder/claude-mdgit clone --depth 1 https://github.com/danielmiessler/LadderWhat 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.00424 | $0.00424 |
| Opus 5 | $0.00212 | $0.00212 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
Ladder 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 3d 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.
What it actually says
Ladder — AI Guidance
What Is This?
Ladder is an open source pipeline for systematic improvement: Sources → Ideas → Hypotheses → Experiments → Results, with results feeding back as sources (the loop).
Key Conventions
- IDs: Each collection uses a prefix:
SR-,ID-,HY-,EX-,AL-,RE-followed by 5-digit zero-padded number - Format: All entries are markdown with YAML frontmatter
- Status values:
draft,active,testing,complete,archived - Linking: Entries reference upstream items (e.g., a hypothesis links to its parent idea via
idea: ID-00001) - CLI: Use
bun run ladder <command>— never npm/npx
Directory Structure
Sources/— Raw inputs (papers, articles, observations, telemetry)Ideas/— Candidate solutions generated from sourcesHypotheses/— Testable predictions from ideasExperiments/— Structured tests with methodologyAlgorithms/— Proven methods for specific tasksResults/— Verified outcomes from experimentsTools/— TypeScript CLI tooling (bun-based)
When Adding Entries
- Use the CLI:
bun run ladder add <type> --title "..." - Or create manually following the TEMPLATE.md in each directory
- Always include all required frontmatter fields
- Link to upstream entries where applicable
- Use the next available ID number
Pipeline Flow
Sources → Ideation → Ideas → Hypotheses → Experiments → Results
↑ |
└──────────────────────── Loop ──────────────────────────┘
Results feed back as sources. This is the core mechanic.
Code Style
- TypeScript only, bun runtime
- No Python, no npm/npx
- Minimal dependencies
- CLI-first philosophy
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.
- 3d ago First seen · 49 lines · 424 tokens per session scan A 39639a7bce4c
Ladder CLAUDE.md is an instructions file published in the GitHub repository danielmiessler/Ladder (261 stars, last pushed 5mo ago), licensed MIT. It adds 424 tokens to every session, about $0.0021 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.