Borrowing it
Nothing to install: this file belongs to avirajkhare00/yoyo. 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/avirajkhare00/yoyo/main/CLAUDE.mdgit clone --depth 1 https://github.com/avirajkhare00/yoyoWrote 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/avirajkhare00/yoyo/claude-md)<a href="https://agentmods.dev/instructions/avirajkhare00/yoyo/claude-md"><img src="https://agentmods.dev/badge/instructions/avirajkhare00/yoyo/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/avirajkhare00/yoyo/claude-md"><img src="https://agentmods.dev/badge/instructions/avirajkhare00/yoyo/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.01221 | $0.01221 |
| Opus 5 | $0.00611 | $0.00611 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
yoyo 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 10d 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.
This is a copy
98% identical to yoyo AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
yoyo — Instructions for Claude
Operator
Read AVIRAJ.md once per session when context is fresh. It defines the operator's standards, pace, and communication style.
Core stance
- Dogfood yoyo in every yoyo session. Pain felt while using it is product input; file an issue when it matters.
- Build feedback loops, not just features. Every change should have a way to measure whether it helped.
- Prefer durable design over extra instructions. If a rule keeps appearing, push it into the product.
Architecture
yoyo has two layers:
- Engine:
src/engine/,src/lang/. Stable core: AST parsing, indexing, analysis, graph operations. - Presentation:
src/mcp.rs,src/cli.rs. MCP schemas, CLI commands, formatting.
Work bottom-up. Fix engine problems in the engine, not with presentation-layer workarounds.
MCP vs CLI
- MCP is the curated surface. Every exposed tool costs tokens; keep only tools that earn their slot.
- CLI is the full human surface. Do not remove CLI commands just because the MCP surface was simplified.
If the boundary is unclear, read docs/architecture.md.
Documentation ownership
Every fact should have one home:
- Language support and project metrics:
METRICS.md - Competitive landscape:
COMPETITORS.md - Version history:
CHANGELOG.md - Architecture and working rules:
CLAUDE.md - Tool and API docs:
docs/README.md
README.md is a front door, not a database. Summarize there and link outward. Delete duplicated facts on sight.
Language ground truth
Before generating code in a systems language, read the relevant playbook when one exists.
- Zig 0.15.x:
playbook/zig-0.15.md
When integrating a new language or library, read the source first. For tree-sitter grammars, inspect:
src/node-types.jsongrammar.jsqueries/highlights.scm
Docs and memory drift; source is ground truth.
Language policy
Use systems languages only:
- Rust for core product code
- Go for tooling, automation, eval harnesses, CI helpers
- Zig when it is the right low-level fit
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.
- 10d ago First seen · 146 lines · 1,221 tokens per session scan A 3e881edf5f77
yoyo CLAUDE.md is an instructions file published in the GitHub repository avirajkhare00/yoyo (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 1,221 tokens to every session, about $0.0061 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to yoyo AGENTS.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
weld copilot-instructions.md
Copilot instructions for configflux/weld: Use @docs/architecture/principles.md for architecture-sensitive changes.
vibecop copilot-instructions.md
Instructions for bhvbhushan/vibecop: After every code edit, run npx vibecop scan --diff HEAD --format agent and fix any findings before proceeding.
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.
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.
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).
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).