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/rasimme/flowboard/agents-mdgit clone --depth 1 https://github.com/rasimme/FlowBoardWhat 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.00450 | $0.00450 |
| Opus 5 | $0.00225 | $0.00225 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
FlowBoard AGENTS.md scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`http://127.0.0.1:18790`. Use a local-capable tool (exec / curl / node) for What it actually says
FlowBoard — agent entry point
FlowBoard coordinates work through the dashboard API at
http://127.0.0.1:18790. Use a local-capable tool (exec / curl / node) for
this localhost API — never an external web-fetch/browser. If an API call
fails, report the blocker; do not infer state.
This file is only the trigger. Everything else is fetched on demand.
Start here
- Check your status:
GET /api/status?agentId=<your-id> - If
activeProject === null: no project is active — work normally, don't infer state. - If
activeProject !== null:- Wait for
contextReady(details inrules/error-handling). - Fetch context:
GET /api/projects/<activeProject>/bootstrap. This includes the project'sPROJECT.md, which carries project knowledge and the project-specific development rules — read them before changing code. - Treat
GET /api/projects/<activeProject>/tasks(the Operational Task State) as the only current-task truth — notPROJECT.md. - Load rule sections on demand:
GET /api/projects/<activeProject>/rules/<section>—commands,api-access,hzl,canvas,files,specify,agent-bridge,error-handling,key-principles,overview.
- Wait for
Where things live
- Project-specific development rules (how to develop this project): the project's
PROJECT.md, served viabootstrap. - Repo / product conventions (commit style, English-only UI strings):
CONTRIBUTING.md. - Task execution & delegation:
rules/agent-bridge+rules/api-access. Build spawn prompts withdashboard/hzl-service.js:buildSpawnPrompt()— do not hand-write them. - External agents (Codex, Cursor, Claude Code, …): see README §
"Using FlowBoard with external agents" and
node dashboard/install-trigger.mjs.
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.
- 2d ago First seen · 34 lines · 450 tokens per session scan A a4a5a7ad0755
FlowBoard AGENTS.md is an instructions file published in the GitHub repository rasimme/FlowBoard (94 stars, last pushed 4d ago), licensed MIT. It adds 450 tokens to every session, about $0.0022 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
veritas-kanban AGENTS.md
Instructions for BradGroux/veritas-kanban, covering agents.md — canonical agent instructions for veritas kanban, runtime requirements, repository layout, essential commands and install.
veritas-kanban CLAUDE.md
Instructions for BradGroux/veritas-kanban, covering claude.md — claude-specific supplement for veritas kanban, what changed in v2.1, lessons learned (claude-specific), security and architecture.
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.
jjj CLAUDE.md
Instructions for doug/jjj, covering claude.md, project overview, build commands, rust cli and vs code extension.
jjj AGENTS.md
Instructions for doug/jjj, covering agent instructions, before you write anything, read this first, house rules and verifying changes to this repository.
sideboard CLAUDE.md
Instructions for mmyslin/sideboard: Sideboard's own roadmap lives in GitHub Issues (mmyslin/sideboard). The project is GitHub-only — there is no roadmap.json / local-file mode.