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/stevenke1981/coart/agents-mdgit clone --depth 1 https://github.com/stevenke1981/coartWrote 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/stevenke1981/coart/agents-md)<a href="https://agentmods.dev/instructions/stevenke1981/coart/agents-md"><img src="https://agentmods.dev/badge/instructions/stevenke1981/coart/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.00291 | $0.00291 |
| Opus 5 | $0.00146 | $0.00146 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
coart 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 3d 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
Coart Agent Development Rules
Mission
Build Coart as an independent clean-room implementation of a Codex-native visual canvas. Preserve functional goals, not Cowart code, wording, icons, screenshots, or branding.
Required workflow
- Read
spec.md,architecture.md,plan.md, andtodos.mdbefore changing code. - Keep the MCP protocol, filesystem layer, frontend bridge, and tldraw UI separated.
- Update or add tests for path, storage, prompt, and insertion behavior.
- Run
npm run check,npm test, andnpm run buildbefore marking work complete. - Record failures, boundaries, and follow-up work in
final.mdandtodos.md.
Safety gates
- Never allow canvas assets to escape the configured
canvas/directory. - Never put secrets or provider API keys in snapshots or browser localStorage.
- Do not delete user images or shapes unless the operation explicitly acknowledges replacement.
- Do not use force push or destructive filesystem deletion without user confirmation.
Architecture rules
- Avoid a monolithic
App.jsx; feature UI belongs insrc/components, bridge logic insrc/lib, and persistence inmcp/lib. - MCP tools must use Zod schemas and return structured content.
- All Widget resources must be CSP-safe and self-contained.
- New shape metadata must be namespaced with
coart.
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.
- 3d ago First seen · 28 lines · 291 tokens per session scan A cf2d41597b4f
coart AGENTS.md is an instructions file published in the GitHub repository stevenke1981/coart (1 stars, last pushed 1mo ago), licensed MIT. It adds 291 tokens to every session, about $0.0015 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).
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.