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/novadiem-studio/bureau/agents-mdgit clone --depth 1 https://github.com/Novadiem-Studio/bureauWrote 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/novadiem-studio/bureau/agents-md)<a href="https://agentmods.dev/instructions/novadiem-studio/bureau/agents-md"><img src="https://agentmods.dev/badge/instructions/novadiem-studio/bureau/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.1 | $0.01979 | $0.01979 |
| Opus 5 | $0.00989 | $0.00989 |
| Sonnet 5 | $0.00396 | $0.00396 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
bureau 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 5d 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.
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.
- 5d ago First seen · 145 lines · 1,979 tokens per session scan A 8cafdaa54964
bureau AGENTS.md is an instructions file published in the GitHub repository Novadiem-Studio/bureau (2 stars, last pushed 2d ago), with no licence file. It adds 1,979 tokens to every session, about $0.0099 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
ai-platform-engineering AGENTS.md
AGENTS.md instructions for caipe-io/ai-platform-engineering, covering agent instructions, project structure, find the canonical implementation, documentation and docs & spec rules.
openhermit AGENTS.md
AGENTS.md instructions for HCF-STUDIOS/openhermit, covering openhermit workspace rules, general, code changes, testing and commits.
playbooks CLAUDE.md
Instructions for playbooks-ai/playbooks, covering claude.md, project overview, core architecture, framework components and key architectural insights.
agent-workflows AGENTS.md
Instructions for sjarmak/agent-workflows, covering agent instructions, quick reference, zfc enforcement, review checklist for agents and compliant patterns to preserve.
ai-platform-engineering CLAUDE.md
Claude Code instructions for caipe-io/ai-platform-engineering, a project described as: CAIPE is an open-source AI platform for building, deploying, governing, and operating AI agents and agentic workflows for platform engineering and beyond.
forge-orchestrator CLAUDE.md
Claude Code instructions for tarunms7/forge-orchestrator, covering workflow orchestration, 1. plan mode default, 2. subagent strategy, 3. self-improvement loop and 4. verification before done.