touchstone CLAUDE.md

A project instruction file that loads the Touchstone development method into every coding session. It also records tests to run when changing Touchstone itself.

In plain words
What is it for?
Use it when developing Touchstone, reviewing its external-review tools, or changing its installer. It points to the relevant checks for those changes.
Why use it?
It keeps the agent aware of this repository’s working method and helps prevent changes from being left untested.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/devdacian/touchstone/claude-md
Clone the repo
git clone --depth 1 https://github.com/devdacian/touchstone
Per session 230 This file is loaded in full into every session.
When invoked 230 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00230 $0.00230
Opus 5 $0.00115 $0.00115
Sonnet 5 $0.00046 $0.00046
Haiku 4.5 $0.00023 $0.00023

Measured 2d ago against content hash 71ab3adbcc42, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

touchstone 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 2d 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.

CLAUDE.md · 21 lines

What it actually says

Claude Code entry (Touchstone source repo)

This repo develops Touchstone and dogfoods it on itself; the methodology lives under .touchstone/methodology/. Because Touchstone is always relevant here, this entry file eager-imports the full methodology so every session has it loaded:

@.touchstone/methodology/TOUCHSTONE.md @.touchstone/methodology/TOUCHSTONE-claude.md

This repo's own dogfood tests for the external-review machinery live in tests/external-review/ (NOT under .touchstone/methodology/, so they are never vendored into hosts). When you change the classifier or wrappers under .touchstone/methodology/scripts/external-review/, run and keep them green: bash tests/external-review/test-classifier.sh and bash tests/external-review/test-forward-wrapper-argv.sh and bash tests/external-review/test-reverse-wrapper-argv.sh.

When you change install.sh, run and keep green: bash -n install.sh and bash tests/test-install-output.sh.

Changes

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.

  1. 2d ago First seen · 21 lines · 230 tokens per session scan A 71ab3adbcc42

Subscribe to this mod's changes

touchstone CLAUDE.md is an instructions file published in the GitHub repository devdacian/touchstone (19 stars, last pushed 1mo ago), licensed MIT. It adds 230 tokens to every session, about $0.0011 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.

Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens