Borrowing it
Nothing to install: this file belongs to bitcraft-apps/spec-first. 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/bitcraft-apps/spec-first/main/AGENTS.mdgit clone --depth 1 https://github.com/bitcraft-apps/spec-firstWrote 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/bitcraft-apps/spec-first/agents-md)<a href="https://agentmods.dev/instructions/bitcraft-apps/spec-first/agents-md"><img src="https://agentmods.dev/badge/instructions/bitcraft-apps/spec-first/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/bitcraft-apps/spec-first/agents-md"><img src="https://agentmods.dev/badge/instructions/bitcraft-apps/spec-first/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.00633 | $0.00633 |
| Opus 5.5 | $0.00253 | $0.00253 |
| Sonnet 5.5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
spec-first 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 1mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Spec First — minimalist development workflow.
Core Philosophy
Build the smallest thing that works. Challenge assumptions. Deliver incrementally.
Principles
- YAGNI: Don't build it until you need it
- KISS: Simplest solution that works
- SRP: Each component does one thing
- MVP First: Deliver narrowest viable change
Anti-Patterns
- Enterprise solutions without justification
- Blind pattern following
- Assumptions without clarification
- Features without immediate need
- Complexity without clear value
Size Constraints
- Agents: 50 lines max
- Skills: 75 lines max
- Workflow scripts: 200 lines max
- Self-documenting through clear naming
Development Checklist
- Can it be smaller? → Make it smaller
- Is it needed now? → If no, skip it
- Does it assume? → Make it ask instead
- Is it complex? → Simplify or remove
- Does it work? → Ship it, iterate later
Documentation Rules
- Minimum viable docs. Document what the user needs to know. If a feature is automatic and invisible, one sentence is enough.
- No duplication. Agent files are the source of truth for agent details. Do not re-list agent names, tools, or descriptions in docs that readers can find in
agents/. - No speculative content. Do not add troubleshooting for problems nobody has reported. Do not document rationale unless the design is surprising.
- Proportional to the change. A one-line config change does not need a new section, glossary entries, ASCII diagrams, or worked examples. Match doc weight to change weight.
- No branding internal mechanics. Do not invent terms for simple concepts. Say what it does plainly.
- User guide = user actions only. If the user doesn't need to do anything, don't explain the internals.
- Technical reference = contract surface. Document interfaces and schemas. Do not duplicate orchestration flows already defined in skill files.
PR Rules
- Every PR must reference a GitHub issue. Use
Closes #<number>in the PR body to auto-close the issue on merge. If no issue exists, create one first.
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.
- 1mo ago First seen · 65 lines · 633 tokens per session scan A 94abe55dbb14
spec-first AGENTS.md is an instructions file published in the GitHub repository bitcraft-apps/spec-first (4 stars, last pushed yesterday), licensed MIT. It adds 633 tokens to every session, about $0.0025 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.