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/harun-yardimci/agentflow/gemini-mdgit clone --depth 1 https://github.com/harun-yardimci/agentflowWrote 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/harun-yardimci/agentflow/gemini-md)<a href="https://agentmods.dev/instructions/harun-yardimci/agentflow/gemini-md"><img src="https://agentmods.dev/badge/instructions/harun-yardimci/agentflow/gemini-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.00378 | $0.00378 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
agentflow GEMINI.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 4d 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.
What it actually says
AgentFlow — Project Context for Gemini CLI
What is this project?
AgentFlow is an AI agent orchestration platform. It runs multi-step pipelines where each task is executed by a CLI coding agent (Claude Code, Codex CLI, or Gemini CLI). It has a React dashboard for monitoring and an MCP server for programmatic control.
Commands
npm run dev— Start frontend + backend with hot reload (port 3100)npm test— Run tests with vitestnpm run lint— ESLintnpm run build— Build frontend
Tech Stack
- Frontend: React 19, TypeScript (strict mode), Tailwind CSS v4, Vite 7
- Backend: Express 5, better-sqlite3, Zod validation
- MCP: @modelcontextprotocol/sdk (stdio + SSE)
- Database: SQLite (
data/agentflow.db, gitignored)
Structure
src/— React frontend (components, context, lib, types)server/— Express backend (db, engine, executor, routes, services, safety)mcp/— MCP serverbin/— CLI entry point
Important Rules
- TypeScript strict mode, no
any— useunknown+ type guards - ESM imports only, no CommonJS
require() - 2-space indent, single quotes in TypeScript
- Functional React components only
- Tailwind utility-first CSS, use
cn()for conditional classes - Commit format:
type(scope): description - Port 3100 is the default backend port
- When spawning CLI processes, always close stdin (
proc.stdin.end()) - No geometric unicode characters in UI (IBM Plex Mono doesn't render them)
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.
- 4d ago First seen · 39 lines · 378 tokens per session scan A 82520cc9305a
agentflow GEMINI.md is an instructions file published in the GitHub repository harun-yardimci/agentflow (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 378 tokens to every session, about $0.0019 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.