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/mkwatson/ai-fastify-template/agents-mdgit clone --depth 1 https://github.com/mkwatson/ai-fastify-templateWrote 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/mkwatson/ai-fastify-template/agents-md)<a href="https://agentmods.dev/instructions/mkwatson/ai-fastify-template/agents-md"><img src="https://agentmods.dev/badge/instructions/mkwatson/ai-fastify-template/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.03628 | $0.03628 |
| Opus 5 | $0.01814 | $0.01814 |
| Sonnet 5 | $0.00726 | $0.00726 |
| Haiku 4.5 | $0.00363 | $0.00363 |
Grade A, and why
ai-fastify-template 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.
How it starts
The opening of the file, as written. The whole thing β 505 lines β stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Guidelines for ai-fastify-template
π¨ CRITICAL: Zero CI Failures Guaranteed
Four-Layer Defense System prevents any CI failures:
- Immediate Feedback (Claude Code hooks):
- Automatic: Validates on every file edit (<2s)
- Shows errors/warnings inline during AI sessions
- Auto-formats code and provides contextual alerts
- During Development:
- Manual:
pnpm ai:quick(run frequently, <5s) - Automatic:
pnpm ai:watch(continuous validation on file save)
- Manual:
- Before Commit: Pre-commit hooks (automatic, ~30s)
- Before Push: Pre-push validation (mandatory, matches CI exactly)
You CANNOT push code that will fail CI - multiple layers ensure quality.
Development validation pipeline:
# Manual validation
pnpm ai:quick # Fast feedback during coding (~5s): lint + type-check (Nx cached)
pnpm ai:check # Standard validation (~30s): + graph validation
pnpm ai:compliance # Full validation (~3min): + tests + build + mutation testing + security
pnpm ai:mutation # Run mutation testing directly (focused on business logic)
# Test configuration validation (CRITICAL)
pnpm test:config:verify # Full validation: property comparison + test execution
pnpm test:config:quick # Fast validation for pre-push hooks
# Continuous validation (runs on file save)
pnpm ai:watch # Watch all files, run ai:quick on changes
pnpm dev:watch # Watch all files, run affected lint+type-check
# Nx affected commands - only run on changed packages
pnpm affected:lint # Lint only changed packages
pnpm affected:test # Test only changed packages
pnpm affected:build # Build only changed packages
pnpm affected:all # Run all tasks on changed packages
Fix issues immediately:
pnpm lint:fix # Auto-fix formatting and linting
Key Rule: The pre-push hook automatically runs pnpm ci:check - you literally cannot push failing code.
Quick Start Essentials
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 Β· 505 lines Β· 3,628 tokens per session scan A 816182910ee6
ai-fastify-template AGENTS.md is an instructions file published in the GitHub repository mkwatson/ai-fastify-template (18 stars, last pushed 1y ago), licensed MIT. It adds 3,628 tokens to every session, about $0.0181 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.