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/abuiles/agents-kanban/agents-mdgit clone --depth 1 https://github.com/abuiles/agents-kanbanWrote 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/abuiles/agents-kanban/agents-md)<a href="https://agentmods.dev/instructions/abuiles/agents-kanban/agents-md"><img src="https://agentmods.dev/badge/instructions/abuiles/agents-kanban/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.00427 | $0.00427 |
| Opus 5 | $0.00214 | $0.00214 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
agents-kanban 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.
What it actually says
AGENTS.md
Scope
This repo runs on Cloudflare Workers.
Do not rely on memory for Cloudflare APIs, limits, bindings, or product behavior. Check current docs first.
Cloudflare docs
Use the official docs for any Workers-related work:
https://developers.cloudflare.com/workers/https://docs.mcp.cloudflare.com/mcp
For limits and quotas, use the product-specific platform/limits page.
Examples:
https://developers.cloudflare.com/workers/platform/limits/https://developers.cloudflare.com/d1/platform/limits/
Products covered by this rule
Always refresh docs before changing code that touches:
- Workers
- Durable Objects
- KV
- R2
- D1
- Queues
- Vectorize
- Workers AI
- Agents SDK
- AI Gateway
Commands
Common commands in this repo:
yarn testyarn typechecknpx wrangler devnpx wrangler deploynpx wrangler types
If bindings change in wrangler.jsonc, run:
npx wrangler types
Validation before commit or push
Before committing or pushing code changes:
- Run
yarn typecheck - Run
yarn test
If either fails, do not commit or push until the failure is fixed or clearly explained.
Runtime references
Useful references:
- Node compatibility:
https://developers.cloudflare.com/workers/runtime-apis/nodejs/ - Workers errors:
https://developers.cloudflare.com/workers/observability/errors/
SECURITY
- NEVER commit API keys.
- NEVER commit
.dev.vars. wrangler.jsonccontains Cloudflare account IDs (not secret but don't expose). If an ID gets added then interpolate it like this:
{
"binding": "TENANT_DB",
"database_name": "my-sandbox-tenant-db",
"database_id": "${TENANT_DB_ID}"
}
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 · 80 lines · 427 tokens per session scan A 0bcc850b2aa3
agents-kanban AGENTS.md is an instructions file published in the GitHub repository abuiles/agents-kanban (11 stars, last pushed 5mo ago), licensed MIT. It adds 427 tokens to every session, about $0.0021 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
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.