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/sirsjg/flux/agents-mdgit clone --depth 1 https://github.com/sirsjg/fluxWrote 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/sirsjg/flux/agents-md)<a href="https://agentmods.dev/instructions/sirsjg/flux/agents-md"><img src="https://agentmods.dev/badge/instructions/sirsjg/flux/agents-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.01140 | $0.01140 |
| Opus 5 | $0.00570 | $0.00570 |
| Sonnet 5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
flux 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 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI agents when working with code in this repository.
Project Overview
Flux is a Kanban board application with multi-project support, designed for both web UI and AI assistant integration via MCP (Model Context Protocol). It's a TypeScript monorepo with five packages sharing a common data store.
Dogfooding
This repo uses Flux to manage itself. Tasks live on flux-data branch:
flux pull # Get latest tasks
flux ready # Show unblocked tasks
flux push "message" # Push task changes
Common Commands
Development
# Start API server (port 3000)
bun --filter @flux/server dev
# Start web dev server (port 5173, proxies API to :3000)
bun --filter @flux/web dev
Build & Test
bun run build # Build all packages
bun run typecheck # Type check all packages
bun run test # Run tests
CLI
cd packages/cli && bun link # Link globally
flux init # Initialize in a repo
flux ready # Show ready tasks
flux task create <project> <title> -P 0 # Create P0 task
Docker
docker build -t flux-mcp .
# Mount repo's .flux directory (SQLite for better concurrency)
docker run -d -p 3000:3000 -v $(pwd)/.flux:/app/packages/data -e FLUX_DATA=/app/packages/data/flux.sqlite flux-mcp
Architecture
CLI (core, standalone) Server (optional)
├── Per-repo .flux/ ├── Web dashboard for .flux/
├── Git-native sync ├── SSE for live updates
├── Works offline ├── Future: multi-repo aggregator
└── Zero dependencies └── Reads same JSON as CLI
packages/
├── cli/ # CLI tool - core, standalone
├── shared/ # Core types and storage abstraction
├── web/ # Preact frontend (optional dashboard)
├── server/ # Multi-repo aggregator (optional)
└── mcp/ # MCP server for LLM integration
Key architectural decisions:
- CLI is the core, works standalone with git-native sync
- Server is optional - aggregates tasks across multiple repos
- Each repo has
.flux/data.jsonsynced viaflux-databranch - Tasks have P0/P1/P2 priority levels for agent task ordering
- Tasks can depend on other tasks/epics; blocked tasks show visual indicators
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 · 157 lines · 1,140 tokens per session scan A 6b8214bd3f40
flux AGENTS.md is an instructions file published in the GitHub repository sirsjg/flux (99 stars, last pushed 7d ago), licensed MIT. It adds 1,140 tokens to every session, about $0.0057 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-30.
Other instructions, from other repositories
kaneo CLAUDE.md
Claude Code instructions for usekaneo/kaneo, a project described as: 🎯 All you need. Nothing you don't. Open source project management that works for you, not against you.
veritas-kanban AGENTS.md
AGENTS.md instructions for BradGroux/veritas-kanban, covering agents.md — canonical agent instructions for veritas kanban, runtime requirements, repository layout, essential commands and install.
kanban CLAUDE.md
Claude Code instructions for kanban-rs/kanban, covering claude.md, project overview, architecture philosophy, solid principles applied and workspace structure.
Chorus CLAUDE.md
Claude Code instructions for Chorus-AIDLC/Chorus, covering claude.md — chorus project guide, what is chorus, tech stack, project structure and key commands.
oh-my-symphony AGENTS.md
Instructions for cskwork/oh-my-symphony, covering agents.md: codex cli entry point, source of truth: skills/symphony-skill, available skill (operator-facing), symphony-skill and worker-side guidance.
kagan AGENTS.md
Instructions for kagan-sh/kagan, covering agents.md, commands, build and package, code map and architecture constraints.