Borrowing it
Nothing to install: this file belongs to loki-ai-ch/spec-manager. 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/loki-ai-ch/spec-manager/main/AGENTS.mdgit clone --depth 1 https://github.com/loki-ai-ch/spec-managerWrote 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/loki-ai-ch/spec-manager/agents-md)<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/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/loki-ai-ch/spec-manager/agents-md"><img src="https://agentmods.dev/badge/instructions/loki-ai-ch/spec-manager/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.00602 | $0.00602 |
| Opus 5.5 | $0.00241 | $0.00241 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
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 2mo 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 — 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 advancesdraft -> frozen. After writing spec content, stop and wait for approval. - Before creating a new spec, inspect existing specs and decisions with
spec-manager spec listandspec-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
standardorgovernedProfile snapshot;governedrequires the frozen L3 to declare## 关键验收标准with valid AC IDs, and task complete requires successful verification evidence covering every critical AC.standardreports missing coverage as warnings. Usespec-manager project profile recommend --request "<work>"for a deterministic, explainable recommendation; it does not auto-enable adaptive workflow and is not a hidden gate. Usespec-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. Usespec-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, usespec-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. quickremains a restricted lightweight exception and does not create the full L1/L2/L3/Task chain.- Record execution with
spec-manager task step; finish withspec-manager task complete.
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.
- 2mo ago First seen · 30 lines · 602 tokens per session scan A 03d812698998
spec-manager AGENTS.md is an instructions file published in the GitHub repository loki-ai-ch/spec-manager (5 stars, last pushed 3mo ago), licensed MIT. It adds 602 tokens to every session, about $0.0024 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.