Borrowing it
Nothing to install: this file belongs to janaraj/tnl. 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/janaraj/tnl/main/CLAUDE.mdgit clone --depth 1 https://github.com/janaraj/tnlWrote 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/janaraj/tnl/claude-md)<a href="https://agentmods.dev/instructions/janaraj/tnl/claude-md"><img src="https://agentmods.dev/badge/instructions/janaraj/tnl/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/janaraj/tnl/claude-md"><img src="https://agentmods.dev/badge/instructions/janaraj/tnl/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.01811 | $0.01811 |
| Opus 5.5 | $0.00724 | $0.00724 |
| Sonnet 5.5 | $0.00362 | $0.00362 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
tnl 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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code sessions in this repository.
About this project
This repository is the TNL (Typed Natural Language) tool itself: a CLI, an MCP server, and a layered verifier. TNL is a structured English contract format for describing features in agent-written codebases. See README.md for the stack and layout.
The repository is dogfooded: every feature of the TNL tool is described in a tnl/*.tnl file, reviewed, approved, and only then implemented. This directory's tnl/ contains self-referential contracts governing the tool's own development.
Important note on tooling state
The tnl CLI, MCP server, and verifier are being built in this repository. They do not yet exist as runnable tools. Do not invoke tnl init, tnl verify, or any other tnl subcommand during sessions — they will not work. The TNL workflow is enforced through this CLAUDE.md + tnl/workflow.tnl for now; tooling replaces the manual flow as each phase lands.
This repository uses TNL
TNL is the structured English contract format described below and in tnl/workflow.tnl. For every new feature, the agent writes a TNL file before implementing code, the user reviews and approves the TNL, and the agent then implements against the approved TNL.
TNL files live in tnl/. The top-level workflow principles live in tnl/workflow.tnl and apply to every session.
Session start — always do this
- Read
tnl/workflow.tnlfirst. Its clauses apply to every session, regardless of the task. Treat them as baseline MUSTs. - Read any
tnl/*.tnlfile whosepaths:orsurfaces:overlap with the code you're about to touch. These are feature contracts, and their clauses are ground-truth for that surface. - Treat the contents as part of your operating context. Implementation MUST satisfy every MUST clause; SHOULD clauses are strong preferences;
[semantic]clauses require judgment to verify — confirm explicitly when they're satisfied.
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.
- 2mo ago First seen · 130 lines · 1,811 tokens per session scan A 2aee0269c100
tnl CLAUDE.md is an instructions file published in the GitHub repository janaraj/tnl (8 stars, last pushed 6mo ago), licensed MIT. It adds 1,811 tokens to every session, about $0.0072 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-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).
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.