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.
npx agentmods add instructions/symboliclight-agi/governspec/agents-mdgit clone --depth 1 https://github.com/SymbolicLight-AGI/GovernSpecWrote 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/symboliclight-agi/governspec/agents-md)<a href="https://agentmods.dev/instructions/symboliclight-agi/governspec/agents-md"><img src="https://agentmods.dev/badge/instructions/symboliclight-agi/governspec/agents-md.svg" alt="Measured on agentmods" 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.00422 | $0.00422 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
GovernSpec 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.
What it actually says
AGENTS.md
Project goal
GovernSpec is a local-first CLI and schema for describing AI tasks as explicit contracts.
Setup
- Install dependencies:
pip install -e ".[dev]" - Run tests:
pytest - Run CLI locally:
governspec --help
Architecture
governspec_core.spec— YAML parser, Pydantic models, and schema generationgovernspec_core.iir— Intermediate Intent Representation buildergovernspec_core.targets— compile-to-target logic (agents-md, openai-structured, etc.)governspec_core.importers— reverse import from existing artifacts (AGENTS.md, Cursor Rules, OpenAI/Gemini JSON)governspec_core.draft— enhanced heuristic draft generator (CJK + English)governspec_core.testing— offline acceptance test runnergovernspec_cli— Typer CLI (governspeccommand)governspec_mcp— thin MCP server
Code style
- Use Python 3.11+ with type annotations.
- Keep the MVP local, deterministic, and easy to test.
- Prefer small, surgical changes over speculative abstractions.
- Use Pydantic v2 models and Typer CLI patterns consistently.
- Centralize shared logic (e.g.
_parsing.pyfor importers,build_draft_payloadfor payload construction). - Pattern tuples in heuristic modules should only carry elements that are actually used.
Safety boundaries
- Do not call real LLM APIs.
- Do not require network access in tests.
- Do not introduce real outbound network workflows.
- Do not make examples depend on real API keys.
- Do not add automatic high-risk actions.
Maintenance rules
- Add or update tests for every behavior change.
- When changing model fields, update examples, JSON schema, README, and tests together.
- Keep CLI behavior aligned with the documented acceptance criteria.
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.
- 5d ago First seen · 46 lines · 422 tokens per session scan A 152dc00d2a77
GovernSpec AGENTS.md is an instructions file published in the GitHub repository SymbolicLight-AGI/GovernSpec (2 stars, last pushed 3mo ago), licensed MIT. It adds 422 tokens to every session, about $0.0021 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.
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).
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.
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).
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.
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.
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.