autospec CLAUDE.md

autospec CLAUDE.md is an instructions file for coding agents from Hundia/autospec. It costs 902 tokens per session, scanned A, original, MIT.

Project instructions for AutoSpec, a framework that manages software work through written specifications and a backlog. They require changes to be tracked, related documentation to stay current, and work to be checked before completion.

In plain words
What is it for?
Use them when implementing fixes, features, or enhancements in an AutoSpec project. They guide backlog updates, documentation changes, and quality checks for areas such as the viewer, command-line tools, and deployment.
Why use it?
They give development work a traceable path from backlog item to verified result. This reduces undocumented changes and prevents incomplete work from being marked done.

Instructions file

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 instructions/hundia/autospec/claude-md
Clone the repo
git clone --depth 1 https://github.com/Hundia/autospec

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.

agentmods badge for autospec CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hundia/autospec/claude-md.svg)](https://agentmods.dev/instructions/hundia/autospec/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/hundia/autospec/claude-md"><img src="https://agentmods.dev/badge/instructions/hundia/autospec/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 902 This file is loaded in full into every session.
When invoked 902 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00902 $0.00902
Opus 5 $0.00451 $0.00451
Sonnet 5 $0.00180 $0.00180
Haiku 4.5 $0.00090 $0.00090

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

Security

Grade A, and why

autospec CLAUDE.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 5d 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.

CLAUDE.md · 102 lines

How it starts

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

Claude Code Memory — AutoSpec

About This Project

AutoSpec is a Spec-Driven Development (SDD) framework. This project develops itself using its own tools. Use /sprint-run, /execute-ticket, /sprint-status etc. in Claude Code.


MANDATORY Development Workflow

Rule 1: Backlog-First Development

Every fix, feature, or change MUST be tracked in specs/backlog.md before or during implementation:

  1. Determine if this is a bug (B.XX), new feature, or enhancement
  2. Add ticket to specs/backlog.md in the appropriate sprint section
  3. Set status to 🔄 In Progress when starting
  4. Set status to ✅ Done when complete

Skip ONLY when user explicitly says "skip backlog", "don't track this"

Rule 2: Living Documentation

Every implemented feature MUST update docs/:

  • Viewer changes → docs/viewer/
  • CLI changes → docs/cli/
  • Methodology changes → docs/methodology/
  • Deployment changes → docs/deployment/
  • New subsystem → create new docs/<subsystem>/ directory

Rule 3: QA Before Done

No ticket is ✅ Done without verification:

Change Type QA Required
Bug fix Reproduce first, fix, verify user flow passes
CLI change npm run build + npm test in cli/
Viewer change npm run build in viewer/ + visual check
Docs/config only No QA — mark ✅ directly
New feature Full test suite + new test cases if needed

Rule 4: Orchestrator + Agent Execution Pattern

This project uses Opus 4.6 as Orchestrator + Sonnet 4.6 as Sprint Agents:

  1. Orchestrator writes agents/sprint-X-brief.md before spawning
  2. Orchestrator spawns: Agent(subagent_type=general-purpose) with briefing
  3. Agent reads brief + relevant specs + docs, implements tickets
  4. Agent updates: specs/backlog.md (🔲→✅), docs/, sprints/sprint-X/summary.md
  5. Orchestrator reviews summary, spawns next sprint(s)

Parallel execution: Sprints with no dependencies run as parallel agents in one message.

Read the full file on GitHub · 102 lines

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.

  1. 5d ago First seen · 102 lines · 902 tokens per session scan A 663de70bbf0a

Subscribe to this mod's changes

autospec CLAUDE.md is an instructions file published in the GitHub repository Hundia/autospec (4 stars, last pushed 2mo ago), licensed MIT. It adds 902 tokens to every session, about $0.0045 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-31.

Related

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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

microsoft/vscode · 5,001 tokens