Borrowing it
Nothing to install: this file belongs to flytohub/flyto-indexer. 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/flytohub/flyto-indexer/main/CLAUDE.mdgit clone --depth 1 https://github.com/flytohub/flyto-indexerWrote 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/flytohub/flyto-indexer/claude-md)<a href="https://agentmods.dev/instructions/flytohub/flyto-indexer/claude-md"><img src="https://agentmods.dev/badge/instructions/flytohub/flyto-indexer/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/flytohub/flyto-indexer/claude-md"><img src="https://agentmods.dev/badge/instructions/flytohub/flyto-indexer/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.02014 | $0.02014 |
| Opus 5 | $0.01007 | $0.01007 |
| Sonnet 5 | $0.00403 | $0.00403 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade B, and why
flyto-indexer CLAUDE.md scanned grade B with 1 finding 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
registered in `.mcp.json` for Claude and `~/.codex/config.toml` for Codex. How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Notes
@AGENTS.md
The rules above are shared with Codex and are the single source of truth. Do not
restate or paraphrase them here — a second copy drifts, and the two agents then
work from different instructions. Repo rules go in AGENTS.md; only the
Claude-specific handoff rules below belong in this file.
Cross-agent handoff
This repo is edited by both Codex and Claude, sometimes on the same day.
- Before starting, read the newest
handoffs/_registry.mdentry and check itsOwnerandBranch. - If an
Activeentry is owned by the other agent, do not edit the same files on the shared branch. Work onclaude/<topic>or pick up different work. - When you finish something durable, write a handoff with
Owner: claudeand the branch you worked on. Conversation-only context is not a release record. - State what you actually verified and what you did not. The other agent will treat your handoff as fact.
Shared code intelligence
Both agents query the same index through the flyto-indexer MCP server —
registered in .mcp.json for Claude and ~/.codex/config.toml for Codex.
- A
post-commithook reindexes this repo automatically, so committed work by the other agent is visible to you. Uncommitted work is not. - If
searchorimpactresults look stale, runflyto-index scan .first. - Agent scratch checkouts under
.claude/worktrees/are excluded from the index. Delete them when the work is merged; they are full copies of the repo.
Code Intelligence (flyto-indexer)
This project is indexed by flyto-indexer. Use its MCP tools for code changes.
First-time setup
If .flyto-index/ does not exist in the project root, run this before using any flyto-indexer tools:
flyto-index scan .
Smart Tools (v2.11+)
flyto-indexer exposes a small set of consolidated MCP tools. Each one auto-enriches results with related data — no need to pick between dozens of granular tools. For code changes, keep the loop closed with pre-change exploration and post-change verification.
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.
- 9d ago First seen · 148 lines · 2,014 tokens per session scan B e4095f105a79
flyto-indexer CLAUDE.md is an instructions file published in the GitHub repository flytohub/flyto-indexer (4 stars, last pushed today), licensed Apache-2.0. It adds 2,014 tokens to every session, about $0.0101 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
Pare copilot-instructions.md
Copilot instructions for Dave-London/Pare, covering pare mcp tools, core rule, tool mapping, pare-git (replaces git) and pare-github (replaces gh).
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).
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.