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/diggerhq/oc-flue-starter/agents-mdgit clone --depth 1 https://github.com/diggerhq/oc-flue-starterWrote 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/diggerhq/oc-flue-starter/agents-md)<a href="https://agentmods.dev/instructions/diggerhq/oc-flue-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/diggerhq/oc-flue-starter/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.00280 | $0.00280 |
| Opus 5 | $0.00140 | $0.00140 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
oc-flue-starter 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.
What it actually says
Working on this starter
This is a stock Flue app deployed to OpenComputer with oc agent deploy. Read PRODUCT.md before
changing its public positioning or examples.
- Keep
agent.tomlmodel aligned with@opencomputer/flue'sDEFAULT_MODEL. - Never commit credentials or generated
dist/,.flue-vite/or.wrangler/output. - Custom tools run in the deployed app. Import every runtime fixture; do not read the git checkout by path.
- Agent-owned skills are packaged imports:
SKILL.mdpluswith { type: 'skill' }, thenskills: [...]. Do not claim they are copied into a workspace. - The default example intentionally has no
sandbox:. AddocSandbox(ctx.env)only for a feature that genuinely needs shell/files, and keep repo workspace support out until it is implemented. - Keep
src/app.tsexporting@opencomputer/flue/app; its/healthroute is part of deploy activation. - Reserved
OC_andFLUE_names belong to the platform. - Keep every README command pasteable in zsh and every demo prompt consistent with
src/data/orders.json.
Validate with npm run typecheck and npm run build. Deploy with oc agent deploy.
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 · 19 lines · 280 tokens per session scan A e101c00ccd8d
oc-flue-starter AGENTS.md is an instructions file published in the GitHub repository diggerhq/oc-flue-starter (2 stars, last pushed 1mo ago), licensed MIT. It adds 280 tokens to every session, about $0.0014 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).
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.
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).
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.