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/wojcikmm/spec-development-protocol/agents-mdgit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWhat 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.04365 | $0.04365 |
| Opus 5 | $0.02183 | $0.02183 |
| Sonnet 5 | $0.00873 | $0.00873 |
| Haiku 4.5 | $0.00436 | $0.00436 |
Grade C, and why
spec-development-protocol AGENTS.md scanned grade C with 1 finding 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Source: local .apm/instructions/coding-standards.instructions.md --> How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Files matching **/*
Global Coding Standards
These apply to all code produced regardless of language, framework, or project type. Adjust specifics to the stack defined in TECH.md.
For SDLC orchestration, gate ordering, agent routing, AGENTS.md context strategy, plan scope budgets, and hardening policy, see @/.github/instructions/sdlc-process.instructions.md — that file is the single source of truth for process. Do not duplicate process rules here; this file governs code quality only.
Code Quality
- Clean Code first: small, focused functions with a single clear responsibility.
- Naming is communication: use intent-revealing names for variables, functions, classes, and files. Avoid abbreviations unless they are universally understood in the domain.
- YAGNI: do not add functionality until it is needed. Avoid speculative abstractions.
- DRY with judgment: eliminate duplication, but do not abstract prematurely. Three occurrences before extracting a shared concept is a reasonable heuristic.
- Avoid deep nesting: prefer early returns, guard clauses, and flat logic over nested conditionals.
- Functions and methods: prefer pure functions where possible. Side effects should be explicit and isolated at system boundaries.
Architecture & Design
- Separation of concerns: keep infrastructure, application logic, and domain rules in separate layers.
- Dependency direction: dependencies should point inward toward domain/core logic, never outward.
- Ports and adapters (Hexagonal): use interfaces/contracts at external boundaries (HTTP, DB, messaging, file system). This keeps the core testable and portable.
- Right-size the design: a simple CRUD endpoint does not need a domain model. A financial transaction processor does. Match complexity to the problem.
- Prefer composition over inheritance.
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.
- 2d ago First seen · 298 lines · 4,365 tokens per session scan C 00d38de52e94
spec-development-protocol AGENTS.md is an instructions file published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 22d ago), licensed MIT. It adds 4,365 tokens to every session, about $0.0218 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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.