Borrowing it
Nothing to install: this file belongs to Chappygo-OS/Atomic-Spec. 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/Chappygo-OS/Atomic-Spec/main/AGENTS.mdgit clone --depth 1 https://github.com/Chappygo-OS/Atomic-SpecWrote 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/chappygo-os/atomic-spec/agents-md)<a href="https://agentmods.dev/instructions/chappygo-os/atomic-spec/agents-md"><img src="https://agentmods.dev/badge/instructions/chappygo-os/atomic-spec/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/chappygo-os/atomic-spec/agents-md"><img src="https://agentmods.dev/badge/instructions/chappygo-os/atomic-spec/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.05287 | $0.05287 |
| Opus 5.5 | $0.02115 | $0.02115 |
| Sonnet 5.5 | $0.01057 | $0.01057 |
| Haiku 4.5 | $0.00529 | $0.00529 |
Grade A, and why
Atomic-Spec 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 1mo 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 — 523 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Adding a New AI Agent to Atomic Spec
About Atomic Spec and the atomicspec CLI
Atomic Spec is a governance framework for AI-driven development — a customized fork of GitHub Spec Kit that enforces the Atomic Traceability Model (gated, atomic, context-pinned phases). See atomic-traceability-model.md for the governance model.
The atomicspec CLI (PyPI package: atomic-spec) bootstraps projects with the framework. It sets up the necessary directory structures, templates, and AI-agent integrations to support the four-phase Specify → Plan → Tasks → Implement workflow.
The framework supports 17+ AI coding assistants across two tiers:
- Supported tier (wired end-to-end, exercised on every release):
claude,gemini,copilot,cursor-agent,windsurf - Experimental tier (template-enforced governance, best-effort triage):
qwen,opencode,codex,kilocode,auggie,codebuddy,qoder,roo,q,amp,shai,bob
Agent matching for subagents is dynamic: keyword overlap between feature descriptions and YAML frontmatter description fields — no hard-coded agent lists in command templates.
This guide explains how to add a new agent to the supported or experimental tier.
General practices
- Any changes to
src/specify_cli/__init__.pyrequire a version rev inpyproject.tomland an entry inCHANGELOG.md. - Agent metadata (
AGENT_CONFIGandATOMIC_SPEC_COMMANDS) lives insrc/specify_cli/_config.py— a stdlib-only module that the release workflow imports viaimportlib.utilwithout installing CLI dependencies.
Adding New Agent Support
This section explains how to add support for new AI agents/assistants to the Specify CLI. Use this guide as a reference when integrating new AI tools into the Spec-Driven Development workflow.
Overview
Specify supports multiple AI agents by generating agent-specific command files and directory structures when initializing projects. Each agent has its own conventions for:
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.
- 1mo ago First seen · 523 lines · 5,287 tokens per session scan A 026da56c4dd1
Atomic-Spec AGENTS.md is an instructions file published in the GitHub repository Chappygo-OS/Atomic-Spec (10 stars, last pushed 1mo ago), licensed MIT. It adds 5,287 tokens to every session, about $0.0211 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.