flyto-ai: Instructions file for Claude Code

CLAUDE.md

flyto-ai CLAUDE.md is an instructions file for Claude Code, Codex from flytohub/flyto-ai. It costs 367 tokens per session, scanned B, a copy of flyto-core CLAUDE.md, Apache-2.0.

Repository instructions for flyto-ai covering shared agent rules, handoffs between Codex and Claude, and code intelligence tools.

In plain words
What is it for?
Checking ownership before coding, reading the latest handoff, using the shared code index, and recording verified work after finishing.
Why use it?
They help agents avoid editing the same files at the same time and preserve a record of completed work for the next agent.

Instructions file for Claude CodeCodex

Written for Codex and Claude Code: reads ~/.codex or $CODEX_HOME, but also the file is CLAUDE.md. Also seen: mentions AGENTS.md; mentions Codex.

This is flytohub/flyto-ai's own configuration. It tells Claude Code and Codex how to work on flyto-ai itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything flyto-ai configures →

Reuse

Borrowing it

Nothing to install: this file belongs to flytohub/flyto-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/flytohub/flyto-ai/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/flytohub/flyto-ai

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for flyto-ai CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/flytohub/flyto-ai/claude-md/github.svg)](https://agentmods.dev/instructions/flytohub/flyto-ai/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/flytohub/flyto-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/flytohub/flyto-ai/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.

agentmods 80×15 button for flyto-ai CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/flytohub/flyto-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/flytohub/flyto-ai/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 367 This file is loaded in full into every session.
When invoked 367 The same file — it is already loaded in full.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00367 $0.00367
Opus 5 $0.00183 $0.00183
Sonnet 5 $0.00073 $0.00073
Haiku 4.5 $0.00037 $0.00037

Measured 8d ago against content hash ffac82632b89, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

flyto-ai 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 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.

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.
Origin

This is a copy

100% identical to flyto-core CLAUDE.md — 0 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.

CLAUDE.md · 33 lines

What it actually says

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.md entry and check its Owner and Branch.
  • If an Active entry is owned by the other agent, do not edit the same files on the shared branch. Work on claude/<topic> or pick up different work.
  • When you finish something durable, write a handoff with Owner: claude and 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-commit hook reindexes this repo automatically, so committed work by the other agent is visible to you. Uncommitted work is not.
  • If search or impact results look stale, run flyto-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.
Changes

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.

  1. 8d ago First seen · 33 lines · 367 tokens per session scan B ffac82632b89

Subscribe to this mod's changes

flyto-ai CLAUDE.md is an instructions file published in the GitHub repository flytohub/flyto-ai (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 367 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 100% identical to flyto-core CLAUDE.md, differing in 0 lines, and is treated as a copy.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens