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/lerianstudio/ring/claude-mdgit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/claude-md)<a href="https://agentmods.dev/instructions/lerianstudio/ring/claude-md"><img src="https://agentmods.dev/badge/instructions/lerianstudio/ring/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.01703 | $0.01703 |
| Opus 5 | $0.00851 | $0.00851 |
| Sonnet 5 | $0.00341 | $0.00341 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
ring 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
AGENTS.md is a symlink to this file — edit CLAUDE.md only; changes propagate automatically.
⛔ CRITICAL RULES (READ FIRST)
1. Agent Modification = Mandatory Verification
When creating or modifying any agent in */agents/*.md:
- MUST verify agent has all required sections — see docs/AGENT_DESIGN.md
- MUST include positive
<example>blocks showing correct behavior - MUST keep agents under 300 lines (implementation) or 200 lines (reviewers)
- MUST use selective standards loading via
index.md(selective sections only, not monolithic WebFetch). - If any section is missing → Agent is INCOMPLETE
2. Agents are EXECUTORS, Not DECISION-MAKERS
- Agents VERIFY, they DO NOT ASSUME
- Agents REPORT blockers, they DO NOT SOLVE ambiguity autonomously
- Agents FOLLOW gates, they DO NOT SKIP gates
- Agents ASK when uncertain, they DO NOT GUESS
3. Anti-Patterns (MUST NOT do these)
- MUST NOT skip ring:using-ring — mandatory, not optional
- MUST NOT run reviewers sequentially — dispatch in parallel
- MUST NOT skip TDD's RED phase — test must fail before implementation
- MUST NOT ignore skill when applicable — "simple task" is not an excuse
- ZERO PANIC POLICY —
panic(),log.Fatal(), andMust*helpers are FORBIDDEN everywhere (including bootstrap/init). Return(T, error)instead. Only exception:regexp.MustCompile()with compile-time constants. - MUST NOT commit manually — use
ring:committing-changesskill - MUST NOT assume compliance — VERIFY with evidence
4. Unified Ring Namespace (MANDATORY)
All Ring components use the unified ring: prefix.
- ✅
ring:code-reviewer,ring:backend-go - ❌ omitting
ring:prefix (FORBIDDEN) - ❌
ring-default:ring:code-reviewer(deprecated plugin-specific prefix)
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 · 149 lines · 1,703 tokens per session scan A 1e22499a6f0b
ring CLAUDE.md is an instructions file published in the GitHub repository LerianStudio/ring (210 stars, last pushed 15d ago), licensed Apache-2.0. It adds 1,703 tokens to every session, about $0.0085 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
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge copilot-instructions.md
Copilot instructions for srnichols/plan-forge, covering instructions for copilot, architecture principles, core principles (non-negotiable), cost estimates and talking to forge-master.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
plan-forge policy.instructions.md
Azure Policy and Initiative compliance — definitions, assignment, compliance state, exemptions, remediation tasks.
plan-forge api-patterns.instructions.md
API patterns for .NET — REST conventions, ProblemDetails, pagination, versioning, error responses.