Borrowing it
Nothing to install: this file belongs to jmanhype/speckit. 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/jmanhype/speckit/main/AGENTS.mdgit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/jmanhype/speckit/agents-md)<a href="https://agentmods.dev/instructions/jmanhype/speckit/agents-md"><img src="https://agentmods.dev/badge/instructions/jmanhype/speckit/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/jmanhype/speckit/agents-md"><img src="https://agentmods.dev/badge/instructions/jmanhype/speckit/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.04083 | $0.04083 |
| Opus 5.5 | $0.01633 | $0.01633 |
| Sonnet 5.5 | $0.00817 | $0.00817 |
| Haiku 4.5 | $0.00408 | $0.00408 |
Grade A, and why
speckit 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 — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Instructions for AI Coding Agents
This file contains workflow rules and guidelines for AI agents (Claude Code, GitHub Copilot, Cursor, Amp, etc.) working in repositories that use Spec Kit + Beads.
Core Philosophy
Spec Kit provides structure (WHAT/WHY/HOW). Beads provides memory (persistent task graph that survives context limits).
Together they solve:
- ✅ Structured specification-driven development
- ✅ Long-term memory across sessions
- ✅ Dependency tracking that doesn't disappear
- ✅ Work discovery and prioritization
Pivotal Methodology Alignment
Spec Kit + Beads implements practices from Pivotal Labs (now VMware Tanzu Labs):
| Pivotal Practice | Spec Kit + Beads Implementation |
|---|---|
| TDD | test-gate.sh enforces 100% test pass after every edit |
| User Stories | spec.md with P1/P2/P3 priorities, [US#] references |
| Story Types | Beads: --type epic/task/bug, labels for chores |
| Story States | Beads: --status todo/in-progress/done/blocked |
| Acceptance Criteria | spec.md ## Acceptance Criteria → Beads epic description |
| IPM (Planning) | /speckit.specify → /speckit.plan → /speckit.tasks |
| Velocity | Beads tracks task completion; bd ready shows unblocked work |
| Dependencies | bd dep add creates blocking relationships (P0 → P1 → P2) |
Pivotal-Style Epic Format
Beads epics created by Spec Kit include:
PROBLEM STATEMENT:
[From spec.md ## Problem Statement]
BUSINESS VALUE:
[From spec.md ## Business Value]
ARCHITECTURAL VISION:
[From plan.md ## Architectural Vision]
INTEGRATION TESTS:
[From spec.md ## Integration Tests]
Acceptance Criteria:
[From spec.md ## Acceptance Criteria]
Blocks (N):
← TASK-1: P0 task description
← TASK-2: P1 task description
...
Priority Levels (Pivotal-Aligned)
| Priority | Pivotal Equivalent | Description |
|---|---|---|
| P0 | Urgent/Blocker | Critical path, blocks everything else |
| P1 | High | MVP features, must-have |
| P2 | Medium | Should-have, important but not blocking |
| P3 | Low | Nice-to-have, future enhancements |
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 · 531 lines · 4,083 tokens per session scan A 523d803eb270
speckit AGENTS.md is an instructions file published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 4,083 tokens to every session, about $0.0163 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-09-01.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.