Borrowing it
Nothing to install: this file belongs to pinecone-io/rings. 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/pinecone-io/rings/main/CLAUDE.mdgit clone --depth 1 https://github.com/pinecone-io/ringsWrote 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/pinecone-io/rings/claude-md)<a href="https://agentmods.dev/instructions/pinecone-io/rings/claude-md"><img src="https://agentmods.dev/badge/instructions/pinecone-io/rings/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/pinecone-io/rings/claude-md"><img src="https://agentmods.dev/badge/instructions/pinecone-io/rings/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.01259 | $0.01259 |
| Opus 5.5 | $0.00504 | $0.00504 |
| Sonnet 5.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 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 — 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.
- 2mo 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 (6 stars, last pushed 25d ago), licensed Apache-2.0. It adds 1,259 tokens to every session, about $0.0050 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.