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/curtisthe/three-pillars-plugin/claude-mdgit clone --depth 1 https://github.com/CurtisThe/three-pillars-pluginWrote 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/curtisthe/three-pillars-plugin/claude-md)<a href="https://agentmods.dev/instructions/curtisthe/three-pillars-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/curtisthe/three-pillars-plugin/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.02442 | $0.02442 |
| Opus 5 | $0.01221 | $0.01221 |
| Sonnet 5 | $0.00488 | $0.00488 |
| Haiku 4.5 | $0.00244 | $0.00244 |
Grade A, and why
three-pillars-plugin 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 4d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ This file is generated — do not edit directly
This CLAUDE.md is shipped from a private dev repo via release.sh. Direct edits to this file (or any other file in this repo's allowlist: skills/, agents/, .claude-plugin/, settings.json, statusline.sh, LICENSE, CONTRIBUTING.md, etc.) will be overwritten on the next release.
To contribute: open an issue or PR describing the change. The maintainer will apply it upstream and re-release. See CONTRIBUTING.md.
Three Pillars Framework
This machine uses the three-pillars skill framework for structured software development with Claude Code.
Project Docs
Every project should maintain four living docs in three-pillars-docs/:
vision.md— Problem, users, principles, non-goals, success signals. Source of truth for why the project exists. Read first by every other TDD skill — it is the filter for what work matters and the tie-breaker when technical options are equivalent. Created by/tp-setupas its first conversational step.architecture.md— System architecture, key decisions, constraints. Source of truth for how the system is built.product_roadmap.md— Current state, design inventory, implementation sequence. Source of truth for what to build next. Links tovision.mdrather than duplicating the why.known_issues.md— Open bugs and limitations by severity. Source of truth for what's broken.
Use /tp-setup first to establish the vision. Then /tp-docs-init to scaffold architecture, roadmap, and known-issues from codebase analysis. Use /tp-docs-update to maintain them after milestones.
Getting Started
Fresh project setup follows a deliberate order — why before how, how before tests:
/tp-setup— Draws out the project's "why" intothree-pillars-docs/vision.md(conversational). Vision only; no test-runner decisions here. Run first on any new project./tp-docs-init— Scaffoldsarchitecture.md,product_roadmap.md, andknown_issues.mdfrom codebase analysis. Usesvision.mdas context./tp-test-setup— Configures test infrastructure (test runner, layout, permissions, starter test). Runs after architecture so test-runner and layout choices are informed by the documented structure, not guessed at before.
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.
- 4d ago First seen · 152 lines · 2,442 tokens per session scan A e80d1c5b005c
three-pillars-plugin CLAUDE.md is an instructions file published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,442 tokens to every session, about $0.0122 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-31.
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.