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/ruvnet/flow-nexus/claude-mdgit clone --depth 1 https://github.com/ruvnet/flow-nexusWrote 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/ruvnet/flow-nexus/claude-md)<a href="https://agentmods.dev/instructions/ruvnet/flow-nexus/claude-md"><img src="https://agentmods.dev/badge/instructions/ruvnet/flow-nexus/claude-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 | $0.03282 | $0.03282 |
| Opus 5 | $0.01641 | $0.01641 |
| Sonnet 5 | $0.00656 | $0.00656 |
| Haiku 4.5 | $0.00328 | $0.00328 |
Grade A, and why
flow-nexus CLAUDE.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 today.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today First seen · 353 lines · 3,282 tokens per session scan A b18fdbbe2ef4
flow-nexus CLAUDE.md is an instructions file published in the GitHub repository ruvnet/flow-nexus (101 stars, last pushed 11mo ago), with no licence file. It adds 3,282 tokens to every session, about $0.0164 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-09-03.
Other instructions, from other repositories
deer-flow copilot-instructions.md
Copilot instructions for bytedance/deer-flow, covering copilot onboarding instructions for deerflow, 1) repository summary, 2) runtime and toolchain requirements, 3) build/test/lint/run - verified command sequences and a. bootstrap and install.
agentfactory CLAUDE.md
Claude Code instructions for stempeck/agentfactory, covering agentfactory, build commands, dependencies, project structure and cli commands.
mavericks-os CLAUDE.md
Claude Code instructions for yahor-punko/mavericks-os, covering claude.md, what this repo is, session start, operational commands and architecture.
harikos.ai AGENTS.md
AGENTS.md instructions for ashyeager/harikos.ai, covering agents.md — harikos ai repository instructions, 1. read first, 2. product definition, 3. mvp means a real saas and 4. reality-only rule.
clarion CLAUDE.md
Claude Code instructions for celanthe/clarion, covering clarion — agent voice manager, what it does, architecture, running it and ui only (edge tts, zero config).
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).