A documentation system for organizing AGENTS.md files and engineering specifications. It separates implementation rules, product requirements, and technical decisions into clearly defined documentation folders.

Auditing, reorganizing, splitting, migrating, and maintaining agent instructions and engineering specifications.

It reduces conflicting or scattered instructions by giving agents a shared map and a single home for each kind of information.

agents-spec — Skill for Claude Code and Codex by leftzzzz: A documentation system for organizing AGENTS.md files and engineering…

Install

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.

agentmods

npx agentmods add skills/leftzzzz/agents-spec-skill/agents-spec

Any agent

npx skills add leftzzzz/agents-spec-skill --skill agents-spec

Clone the repo

git clone --depth 1 https://github.com/leftzzzz/agents-spec-skill

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/leftzzzz/agents-spec-skill/agents-spec.svg)](https://agentmods.dev/skills/leftzzzz/agents-spec-skill/agents-spec)

Your own site

<a href="https://agentmods.dev/skills/leftzzzz/agents-spec-skill/agents-spec"><img src="https://agentmods.dev/badge/skills/leftzzzz/agents-spec-skill/agents-spec.svg" alt="Measured on agentmods" height="20"></a>

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,517 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00098	$0.02517
Opus 5	$0.00049	$0.01259
Sonnet 5	$0.00020	$0.00503
Haiku 4.5	$0.00010	$0.00252

Measured 5d ago against content hash 4052484d7cee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agents-spec 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 5d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/audit_agents_md.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/agents-spec/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS Spec

Core Model

Use a cross-agent documentation model:

Keep root AGENTS.md as the shared boot map and documentation router.
Keep current, implementation-facing engineering standards, contracts, policies, and invariants in docs/specs/ as the single live Spec source.
Keep product intent, acceptance criteria, and product decisions in docs/requirements/.
Keep architecture, implementation plans, and technical decisions in docs/technical/.
Keep real AGENTS.md navigation entrypoints in all three documentation directories.
Do not depend on nested AGENTS.md auto-discovery. Make root explicitly tell every agent when to read or search each directory.
Do not use .agents/projects/ or .agents/references/ as the canonical Spec store.

Use this default layout:

AGENTS.md
CLAUDE.md -> AGENTS.md       # Optional; create only on explicit user request
docs/
  specs/
    AGENTS.md
    projects/
    references/
  requirements/
    AGENTS.md
  technical/
    AGENTS.md

Preserve an existing useful subdivision under docs/specs/; projects/ and references/ are defaults, not mandatory empty directories.

Document Responsibilities

Classify a statement by what it governs:

Agent instruction: state how an agent must act or where it must look.
Engineering Spec: state what the code or system must satisfy now, such as a standard, contract, protocol, security policy, compatibility boundary, or operational invariant.
Requirement document: record the product or business outcome, why it matters, acceptance criteria, and product decisions.
Technical document: record architecture, implementation approach, tradeoffs, and technical decisions.

Do not use docs/specs/ as a generic home for every document called a "spec." Split a mixed document by responsibility: move business intent and acceptance criteria to docs/requirements/, current verifiable engineering constraints to docs/specs/, and design rationale to docs/technical/.

Read the full file on GitHub · 186 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

5d ago First seen · 186 lines · 98 tokens per session scan A 4052484d7cee

Subscribe to this mod's changes

agents-spec is a skill published in the GitHub repository leftzzzz/agents-spec-skill (36 stars, last pushed 15d ago), licensed MIT. It adds 98 tokens to every session and 2,517 once invoked, about $0.0005 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.

Building agents Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens