Borrowing it
Nothing to install: this file belongs to ariel-frischer/autospec. 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/ariel-frischer/autospec/main/AGENTS.mdgit clone --depth 1 https://github.com/ariel-frischer/autospecWrote 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/ariel-frischer/autospec/agents-md)<a href="https://agentmods.dev/instructions/ariel-frischer/autospec/agents-md"><img src="https://agentmods.dev/badge/instructions/ariel-frischer/autospec/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.1 | $0.03173 | $0.03173 |
| Opus 5 | $0.01587 | $0.01587 |
| Sonnet 5 | $0.00635 | $0.00635 |
| Haiku 4.5 | $0.00317 | $0.00317 |
Grade A, and why
autospec 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 8d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents working with this repository.
Prerequisites
- Go 1.25+: Check with
go version - AI coding agent CLI: Authenticated and configured
- Make, golangci-lint: For build/lint (
make lint)
Commands
# Build & Dev
make build # Build for current platform
make test # Run all tests (quiet, shows failures only)
make test-v # Run all tests (verbose, for debugging)
make fmt # Format Go code (run before committing)
make lint # Run all linters
# Single test
go test -run TestName ./internal/package/
# CLI usage (run `autospec --help` for full reference)
autospec run -a "feature description" # All stages: specify → plan → tasks → implement
autospec prep "feature description" # Planning only: specify → plan → tasks
autospec implement --phases # Each phase in separate session
autospec implement --tasks # Each task in separate session
autospec st # Show status and task progress
autospec doctor # Check dependencies
Post-Change Polish (REQUIRED)
After significant code changes, automatically invoke the repo-local polish skill before final handoff. Use it to update changelog/docs and run the required validation targets. Do not wait for an explicit $polish request unless the change is trivial or docs-only.
Core Workflow
Stage Dependencies (MUST follow this order)
constitution → specify → plan → tasks → implement
↓ ↓ ↓ ↓
constitution.yaml spec.yaml plan.yaml tasks.yaml
| Stage | Requires | Produces |
|---|---|---|
constitution |
— | .autospec/constitution.yaml |
specify |
constitution | specs/NNN-feature/spec.yaml |
plan |
spec.yaml | plan.yaml |
tasks |
plan.yaml | tasks.yaml |
implement |
tasks.yaml | code changes |
Constitution is REQUIRED before any workflow stage.
What autospec init Does
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.
- 8d ago First seen · 345 lines · 3,173 tokens per session scan A 068252aad158
autospec AGENTS.md is an instructions file published in the GitHub repository ariel-frischer/autospec (141 stars, last pushed 29d ago), licensed MIT. It adds 3,173 tokens to every session, about $0.0159 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.
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.
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).
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.