Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/flomenco-inc/flo-plugin/agents-mdgit clone --depth 1 https://github.com/Flomenco-Inc/flo-pluginWhat 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 | $0.01342 | $0.01342 |
| Opus 5 | $0.00671 | $0.00671 |
| Sonnet 5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
flo-plugin 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 yesterday.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Context — flo-plugin
This is the public standalone repository for the Flo plugin for Claude.
It was extracted from the flo monorepo (packages/flo-claude-plugin-mcp) on
2026-05-14 to enable public distribution, Anthropic marketplace listing, and
community contributions.
What this repo is
An MCP (Model Context Protocol) server that
bridges Claude (Desktop, Code, or any MCP-capable client) to the Flo AI media
platform. Users install it via npx @flomenco/claude-plugin-mcp — no repo
clone required.
The plugin also serves as the foundation for a Claude Code plugin
(skills, slash commands, marketplace.json) which a coworker is integrating
in a separate PR. See CONTRIBUTING.md for how to add that content.
Repo layout
flo-plugin/
├── src/
│ └── index.js # MCP server entry point — all tool definitions live here
├── tools/
│ ├── install-claude-desktop.js # dev helper: writes claude_desktop_config.json
│ ├── uninstall-claude-desktop.js # dev helper: removes the entry
│ └── print-bootstrap-config.js # dev helper: prints bootstrap JSON for operators
├── .github/
│ └── workflows/
│ └── publish.yml # auto-publish to npm on v* tags
├── .cursor/
│ └── rules/
│ └── flo-plugin.mdc # Cursor rules for this repo
├── AGENTS.md # ← you are here
├── CONTRIBUTING.md
├── README.md
├── LICENSE # MIT
└── package.json
Key facts for LLMs working here
This is a PUBLIC repo — do not add:
- Hardcoded secrets, tokens, or API keys
- Internal-only infra URLs beyond the public
floapp.co/*.floapp.codomains - AWS account IDs or private ARNs
- Employee emails or personal info
- Anything that should not be visible to the open internet
The Cognito hosted-UI domain (flomenco*.auth.us-east-1.amazoncognito.com),
pool names (flo-prod/stg/dev), and OAuth client names are intentionally
public — they are discoverable from any OAuth token's iss claim.
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.
- yesterday First seen · 118 lines · 1,342 tokens per session scan A bddada3f4fc6
flo-plugin AGENTS.md is an instructions file published in the GitHub repository Flomenco-Inc/flo-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 1,342 tokens to every session, about $0.0067 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.