spec-manager AGENTS.md

spec-manager AGENTS.md is an instructions file for Codex, OpenCode from loki-ai-ch/spec-manager. It costs 602 tokens per session, scanned A, original, MIT.

Repository instructions for using spec-manager, a system that records software requirements, designs, decisions, tasks, and audits as files.

In plain words
What is it for?
Use them when adding features to the covered project, especially to inspect existing specs, get approvals, and implement only from a frozen implementation specification.
Why use it?
They impose a required review process before implementation code is written, reducing work based on unapproved or incomplete specifications.

Instructions file for CodexOpenCode

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/loki-ai-ch/spec-manager/agents-md
Clone the repo
git clone --depth 1 https://github.com/loki-ai-ch/spec-manager

Made for: Codex, OpenCode.

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 spec-manager AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/loki-ai-ch/spec-manager/agents-md.svg)](https://agentmods.dev/instructions/loki-ai-ch/spec-manager/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/loki-ai-ch/spec-manager/agents-md"><img src="https://agentmods.dev/badge/instructions/loki-ai-ch/spec-manager/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 602 This file is loaded in full into every session.
When invoked 602 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.1 $0.00602 $0.00602
Opus 5 $0.00301 $0.00301
Sonnet 5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured 5d ago against content hash 03d812698998, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

spec-manager 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 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.

AGENTS.md · 30 lines

How it starts

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

spec-manager Workflow Capsule

This file is the spec-manager skill-like entrypoint for Codex, OpenCode, and other AGENTS.md-compatible tools. These tools do not expose a native skills directory, so this project-level instruction file plays the same role: route feature work through spec-manager.

This project uses spec-manager for spec-driven AI coding workflows. Specs, tasks, decisions, changes, and audit data are stored as markdown/JSON files in the repository.

Mandatory Workflow

  • Feature work MUST go through spec-manager; do not jump directly from a user request to implementation code.
  • New or non-trivial work follows L1 PRD -> L2 Design -> L3 Impl -> Agent Task.
  • Never write implementation code unless the relevant L3 spec is frozen.
  • L1/L2 approval advances draft -> confirmed; one explicit L3 approval advances draft -> frozen. After writing spec content, stop and wait for approval.
  • Before creating a new spec, inspect existing specs and decisions with spec-manager spec list and spec-manager decision list --topic <topic>.
  • Before code edits, read the relevant frozen L3 spec and create/start an Agent Task.
  • If adaptive workflow is enabled, Task creation records a standard or governed Profile snapshot; governed requires the frozen L3 to declare ## 关键验收标准 with valid AC IDs, and task complete requires successful verification evidence covering every critical AC. standard reports missing coverage as warnings. Use spec-manager project profile recommend --request "<work>" for a deterministic, explainable recommendation; it does not auto-enable adaptive workflow and is not a hidden gate. Use spec-manager project profile metrics [--topic <topic>] [--json] for a read-only governance report over Profile adoption, governed coverage gaps, standard warnings, and explicit overrides; metrics does not modify config or historical Tasks. Use spec-manager project readiness critical [--topic <topic>] [--json] for a read-only critical AC readiness report and repair suggestions; it must not auto-generate or insert critical AC. Before enabling adaptive workflow, use spec-manager project workflow preview [--json] for a read-only adoption preview; preview does not write config, migrate historical Tasks, or act as an enable gate.
  • quick remains a restricted lightweight exception and does not create the full L1/L2/L3/Task chain.
  • Record execution with spec-manager task step; finish with spec-manager task complete.

Read the full file on GitHub · 30 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 · 30 lines · 602 tokens per session scan A 03d812698998

Subscribe to this mod's changes

spec-manager AGENTS.md is an instructions file published in the GitHub repository loki-ai-ch/spec-manager (5 stars, last pushed 1mo ago), licensed MIT. It adds 602 tokens to every session, about $0.0030 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.