What is flyto-ai AGENTS.md?

Repository instructions for developing the flyto-ai agent and its connections to AI providers, cloud services, and tools. They define rules for credentials, indexing, validation, evidence, tests, and documentation.

Use them when changing flyto-ai integrations, agent capabilities, or execution flows. They guide work involving typed contracts, guardrails, tracing, tests, documentation, and rollback notes.

They help contributors preserve the project's safety and execution boundaries, especially around secrets and changes that affect multiple components. They also specify that core-tool execution must follow the repository's audited route.

How flytohub/flyto-ai configures Codex and OpenCode

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/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/flytohub/flyto-ai

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/flytohub/flyto-ai/agents-md/github.svg)](https://agentmods.dev/instructions/flytohub/flyto-ai/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/flytohub/flyto-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/flytohub/flyto-ai/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/flytohub/flyto-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/flytohub/flyto-ai/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,499 This file is loaded in full into every session.

When invoked 1,499 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.01499	$0.01499
Opus 5.5	$0.00600	$0.00600
Sonnet 5.5	$0.00300	$0.00300
Haiku 4.5	$0.00150	$0.00150

Measured 2mo ago against content hash d88a1278b069, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

flyto-ai Agent Rules

flyto-ai is the agent/runtime adapter between LLM providers, Flyto2 Cloud, blueprint learning, and flyto-core MCP tools.
Do not store credentials, API keys, cookies, bearer tokens, screenshots containing secrets, or user passwords in source, tests, docs, handoffs, evidence, or generated YAML.
Treat flyto-core as the module/runtime authority. Read its MCP schemas and recipes, but do not modify flyto-core from this repo.
All flyto-core execution must flow through flyto_ai.tools.core_tools so validation, browser retry, permission checks, and MCP evidence metadata stay consistent.
New agent capabilities need a closed loop: typed contract, guardrail, evidence/trace, test, docs, and rollback notes.
Keep .flyto-index/, transcripts, evidence, build output, local DBs, and eval results out of commits.
For deep changes, run flyto-indexer impact/search/verify before finalizing.

Coding Route Rules

The public code-mcp / code-serve service is one audited entry. Host-owned lanes surround whichever implementer startup selected: a mandatory Indexer gate before any model edit and again after the source-controlled checks, a mandatory read-only Blueprint discovery lane, and Core validation. All four lanes are configured on every strict public route; none is detachable, and Blueprint and Core may resolve only applied or not-applicable.
Never let model prose assert that a lane, plan step, or gate ran. A lane outcome must come from a completed allowlisted call recorded in the route receipt.
Do not add a route-bypass flag, do not let a green repository check stand in for the Indexer post-gate, and do not grant the implementer the audit tool, Blueprint execution authority, or Core danger/browser authority.
Core execution keeps flowing through flyto_ai.tools.core_tools. Do not import sibling flyto-core, flyto-blueprint, or flyto-indexer source.
Changing a lane, allowlist, bound, or receipt field is an architecture change: update ARCHITECTURE.md, docs/architecture-map.md, STATE.md, and DECISIONS.md in the same change.

Read the full file on GitHub · 96 lines

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.

2mo ago First seen · 96 lines · 1,499 tokens per session scan A d88a1278b069

Subscribe to this mod's changes

flyto-ai AGENTS.md is an instructions file published in the GitHub repository flytohub/flyto-ai (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,499 tokens to every session, about $0.0060 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.

Workflow Automation ai-agent flyto2 mcp-server procedure-reuse

flyto-ai AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
flyto-ai AGENTS.mdflytohub/flyto-ai	Instructions file	2	1mo ago	Apache-2.0	A	1,499	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

flyto-ai: Instructions file for Codex