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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/flytohub/flyto-indexer/agents-md"><img src="https://agentmods.dev/badge/instructions/flytohub/flyto-indexer/agents-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.1 | $0.00931 | $0.00931 |
| Opus 5 | $0.00465 | $0.00465 |
| Sonnet 5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
flyto-indexer AGENTS.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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Rules
Before changing this repository, read STATE.md, ARCHITECTURE.md,
DECISIONS.md, and the latest entry in handoffs/_registry.md.
flyto-indexeris the local code intelligence and verification tool for Flyto2 repositories.- Keep analysis local by default. Do not introduce network calls for audit, indexing, or verification paths unless explicitly designed and documented.
- Prefer deterministic static analysis, typed impact, dependency, taint, and project-profile checks over ad hoc text scans.
- Generated index artifacts must stay out of source control.
- Do not store credentials, customer source excerpts beyond necessary test fixtures, or local login details in docs, handoffs, tests, or scripts.
- Run
bash scripts/lint-project-memory.shafter editing project memory files.
Gate Remediation Loop
- A gate result with
pass=falseblocks only the requested phase; it does not terminate the task and must not be reported as task completion. - Do not edit or enter the blocked phase while the gate is false. Execute every
in-scope item in
required_actions, updatecurrent_statewith the exact requested keys, and immediately run the same gate again. Repeat untilpass=true. - Missing impact, dependency, test review, or change-plan state is agent-owned remediation, not a user blocker.
- Pause for the user only when remediation requires credentials or other required input, unavailable external authorization or state, or an irreversible human decision.
Flyto2 Project Memory Contract
Every Flyto2 repository must keep this project-memory scaffold current:
AGENTS.md: agent operating rules, repo-specific constraints, verification commands.CLAUDE.md: Claude-facing handoff rules when this repo is edited outside Codex.PROJECT.md: product purpose, owned surfaces, users, and non-goals.ARCHITECTURE.md: module boundaries, runtime shape, data flow, and integration points.STATE.md: current status, known risks, release/deploy state, and last verification.ROADMAP.md: near-term, later, and explicitly out-of-scope work.tasks.md: actionable checklist with owners/status when known.DECISIONS.md: durable architectural/product decisions with dates and rationale.CHANGELOG.md: user-visible or operator-visible changes.docs/README.md: index for durable docs in this repo.workflows/*.md: repeatable agent workflows for idea capture, planning, implementation, bugfix, refactor, investigation, and wrap-up.handoffs/_registry.md: index of handoffs; new handoffs useYYYY-MM-DD-topic.md.
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.
- 8d ago First seen · 64 lines · 931 tokens per session scan A 067463e103f3
flyto-indexer AGENTS.md is an instructions file published in the GitHub repository flytohub/flyto-indexer (4 stars, last pushed today), licensed Apache-2.0. It adds 931 tokens to every session, about $0.0047 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
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.