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/pbakaus/impeccable/agents-mdgit clone --depth 1 https://github.com/pbakaus/impeccableWhat 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.03427 | $0.03427 |
| Opus 5 | $0.01714 | $0.01714 |
| Sonnet 5 | $0.00685 | $0.00685 |
| Haiku 4.5 | $0.00343 | $0.00343 |
Grade A, and why
impeccable 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 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.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
skill/ is the source of truth for the Impeccable skill: SKILL.src.md, reference/, scripts/, and agents/. Build logic lives in scripts/, with provider configs in scripts/lib/transformers/. The CLI and anti-pattern detector live in cli/, the browser extension in extension/, the Astro website in site/, Cloudflare Pages Functions in functions/, and regression coverage in tests/ with fixtures under tests/fixtures/. dist/ and build/ are generated and gitignored. The root harness folders (.agents/, .claude/, .cursor/, etc.) and plugin/ are generated distribution artifacts that are tracked for direct repo installs, not hand-authored source.
Build, Test, and Development Commands
bun run dev- start the local Bun server.bun run build- source-first build: regeneratedist/, derived site assets, and validation output without syncing tracked harness folders.bun run build:release- release/distribution build: run the full build and sync tracked root harness folders plusplugin/.bun run rebuild- clean and rebuild everything from scratch without syncing tracked harness folders.bun run rebuild:release- clean and rebuild everything, including tracked harness output sync.bun test tests/build.test.js- run a focused Bun test.bun run test- run the full Bun + Node test suite (includes the plugin loader E2E, which installs the committedplugin/subtree into a sandboxed real Claude Code and skips cleanly when theclaudeCLI is absent).bun run test:live-e2e- opt-in live-mode E2E against framework fixtures (~2 min; needsnpx playwright install chromiumonce).bun run test:skill-behavior- opt-in LLM-backed checks that the SKILL.md Setup flow actually drives the agent (runs claude-sonnet-5 / gpt-5.6-luna / gemini-3.5-flash / deepseek-v4-flash; needs.envwith provider keys).bun run test:plugin-e2e- just the plugin loader E2E, for fast iteration onplugin/,skill/agents/, orscripts/build.jschanges.bun run build:browser/bun run build:extension- rebuild browser-specific bundles.
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 · 92 lines · 3,427 tokens per session scan A 19284fbc22ae
impeccable AGENTS.md is an instructions file published in the GitHub repository pbakaus/impeccable (64,510 stars, last pushed today), licensed Apache-2.0. It adds 3,427 tokens to every session, about $0.0171 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
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.
buildNext
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
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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
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.
langchain 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.