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/pinecone-io/rings/claude-mdgit clone --depth 1 https://github.com/pinecone-io/ringsWhat 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.01259 | $0.01259 |
| Opus 5 | $0.00629 | $0.00629 |
| Sonnet 5 | $0.00252 | $0.00252 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
rings 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rings — Development Process
Testing
- Implement first, then test. Write the real implementation, then write tests that verify it. Do not write tests first and fill in stubs to make them compile — placeholder implementations are forbidden.
- No
todo!(),unimplemented!(), or stub bodies in committed code. Every committed function must do what it says. - No live
claudeinvocations in tests. The process execution layer must sit behind a trait (e.g.,Executorinsrc/executor.rs) so it can be mocked. Never call an actualclaudesubprocess in any test. - A feature is done when: happy path and key error paths are covered at both unit and integration level.
unwrap()in tests is fine — a panic fails the test, which is the intended behavior.
Code Quality Gates
A task is not done until all of the following are satisfied:
- Tests pass —
just validateis clean (runs fmt-check, lint, and tests) - Formatting — run
just fmtto auto-fix, then re-runjust validate - No
unwrap()orexpect()in production code — all errors propagate via?andanyhow - Spec consulted — the relevant spec in
specs/was read and the implementation is consistent with it. If no directly relevant spec exists, note that inREVIEW.mdunder Open Questions. - REVIEW.md updated — any decisions, conflicts, or open questions from this task are recorded
Commits
Conventional commit prefixes are required:
feat:— new functionalityfix:— bug fixestest:— adding or updating testsrefactor:— code restructuring without behavior changechore:— build, deps, configdocs:— documentation only
Scopes are optional (e.g., feat(executor): ...). No PRs. No branches. Commit directly to main.
Task Tracking
TODO.md at the repo root is the implementation queue. The /build command picks up the next unchecked task from it. The /plan command appends new tasks after planning.
Filing Bugs and Ideas
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.
- 2d ago First seen · 102 lines · 1,259 tokens per session scan A d610a1f4bb36
rings CLAUDE.md is an instructions file published in the GitHub repository pinecone-io/rings (5 stars, last pushed 16d ago), licensed Apache-2.0. It adds 1,259 tokens to every session, about $0.0063 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
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
mq commit.instructions.md
Instructions for harehare/mq: Use the following format for commit messages.
stiletto CLAUDE.md
Instructions for benjamin-bader/stiletto, covering stiletto — contributor & agent guide, commit messages: conventional commits (required), breaking changes, examples and how releases work.
crow CLAUDE.md
Instructions for kh0pper/crow, covering claude.md, working with this repo, network exposure invariant, maintaining claude.md vs crow.md and where to find things.
cotect CLAUDE.md
Instructions for cotect-dev/cotect, covering project conventions and git commits.