Borrowing it
Nothing to install: this file belongs to shbernal/caniemail-ai-tooling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shbernal/caniemail-ai-tooling/main/AGENTS.mdgit clone --depth 1 https://github.com/shbernal/caniemail-ai-toolingWrote 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/shbernal/caniemail-ai-tooling/agents-md)<a href="https://agentmods.dev/instructions/shbernal/caniemail-ai-tooling/agents-md"><img src="https://agentmods.dev/badge/instructions/shbernal/caniemail-ai-tooling/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.04535 | $0.04535 |
| Opus 5 | $0.02268 | $0.02268 |
| Sonnet 5 | $0.00907 | $0.00907 |
| Haiku 4.5 | $0.00453 | $0.00453 |
Grade A, and why
caniemail-ai-tooling 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents working in this repo.
What this is
Two surfaces (an agent skill and an MCP server) over one shared core
(core/caniemail-core.mjs) giving an agent access to email client HTML/CSS
compatibility data. See README.md for the full pitch and usage.
core/ the implementation and its tests, the only real source
skill/ SKILL.md, a CLI, and a vendored copy of the core
mcp/ the mcp-server-caniemail npm package, a thin adapter over the core
The shipped core has zero runtime dependencies. Node 22+ and nothing else.
That is a property to preserve, not an accident: it is what lets skill/ run
from a bare checkout with no package.json and no install step.
Released
Both surfaces are live: mcp-server-caniemail on npm and email-compat on
ClawHub. docs/releasing.md has the process for each.
Which version is current is deliberately not written here. git tag and the top
of CHANGELOG.md both answer it, and a number copied into prose is one more
thing a release has to remember to move. This file went two releases describing
the first one.
Publishing is automated. .github/workflows/publish.yml uploads to npm on a
v* tag push and to ClawHub on a published release, and it re-runs the full
suite on the released ref first. A tag does not match CI's branches: [main]
filter, so without that job the released commit would reach both registries with
nothing verified on it. Both halves are idempotent, so a partly-failed release
can be re-run.
Both registries treat a version as permanent. Never delete or re-publish a released version; fix forward with a version bump on whichever surfaces are affected. The two artifacts are independent and their version numbers are not required to move together. Couple them only when a change reaches both.
Breaking changes are welcome
Released constrains what a published version means, not what the next one may do. When the better behaviour is incompatible with the old one, ship the better behaviour: remove the old one and bump the version.
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.
- yesterday Changed · +16 lines · +207 tokens per session 684d0cd8ea65
- 6d ago First seen · 321 lines · 4,328 tokens per session scan A 0e96515dcc59
caniemail-ai-tooling AGENTS.md is an instructions file published in the GitHub repository shbernal/caniemail-ai-tooling (1 stars, last pushed 2d ago), licensed MIT. It adds 4,535 tokens to every session, about $0.0227 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
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 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).
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.
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.