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/thanhtung2693/specgate/agents-mdgit clone --depth 1 https://github.com/thanhtung2693/specgateWrote 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/thanhtung2693/specgate/agents-md)<a href="https://agentmods.dev/instructions/thanhtung2693/specgate/agents-md"><img src="https://agentmods.dev/badge/instructions/thanhtung2693/specgate/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 | $0.02028 | $0.02028 |
| Opus 5 | $0.01014 | $0.01014 |
| Sonnet 5 | $0.00406 | $0.00406 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
specgate 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 3d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecGate Contributor Rules
These are repository rules for people and coding agents who modify, test,
review, or release SpecGate. They are not instructions installed for SpecGate
product users. Product installation and day-to-day workflows belong in
docs/using-specgate/.
Rule precedence
- Read this file before modifying the repository.
- Read the nearest nested
AGENTS.mdfor every module you touch. Nested files extend this file and may add stricter module rules. CLAUDE.mdis only a Claude Code entry point to these contributor rules; it must not duplicate or replace them.
Product plugin rules under plugins/ and their generated copies describe how
installed IDE agents use SpecGate. They are product assets, not contributor
rules for this repository.
Repository map
| Path | Stack | Responsibility | Contributor docs |
|---|---|---|---|
app/doc-registry/ |
Go 1.26+ | REST API, governance state, Postgres, and object storage | app/doc-registry/AGENTS.md, app/doc-registry/docs/ |
app/agents/ |
Python 3.12+ / LangGraph | Governance chat and model-backed governance operations | app/agents/AGENTS.md, app/agents/docs/ |
app/ui/ |
Vite / React / TypeScript | Web application | app/ui/AGENTS.md, app/ui/docs/ |
app/cli/ |
Go 1.26+ / Cobra | Human- and IDE-agent-facing CLI, Local mode, and installers | app/cli/AGENTS.md, docs/using-specgate/reference/cli.md |
app/landing/ |
Static HTML/CSS/JS | Public landing page | app/landing/README.md |
plugins/ |
Markdown, scripts, manifests | Canonical IDE plugin assets | plugins/README.md |
deploy/, docker/ |
Compose / Docker | Released and contributor deployment packaging | deploy/README.md, docs/contributing/setup.md |
Contributor architecture, contracts, setup, testing, and release guidance live
in docs/contributing/. Product documentation
lives in docs/using-specgate/.
Before editing
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.
- 3d ago First seen · 180 lines · 2,028 tokens per session scan A 0d55618d7b75
specgate AGENTS.md is an instructions file published in the GitHub repository thanhtung2693/specgate (5 stars, last pushed 13d ago), licensed Apache-2.0. It adds 2,028 tokens to every session, about $0.0101 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
meta-llm-charter CLAUDE.md
Instructions for entropyvortex/meta-llm-charter, covering meta v3.1 core charter, bias, meta-0, r1 decompose and r2 ask gate.
awesome-reviewers CLAUDE.md
Instructions for baz-scm/awesome-reviewers, covering awesome reviewers — repository guidelines, what this project is, source of truth, site layer and machine interface.
code-context AGENTS.md
AGENTS.md instructions for infino-ai/code-context, covering code-context: notes for ai agents, project overview, repo map, build, test, gates and conventions.
gtm-cheat-codes AGENTS.md
Instructions for zapier/gtm-cheat-codes, covering agents.md and project overview.
Stata-CLI AGENTS.md
Instructions for Utolaris/Stata-CLI, covering agents.md, project structure and working rules.
tapp AGENTS.md
AGENTS.md instructions for aarwitz/tapp, covering tapp agent playbook, no mcp connected? just run the cli, pick the right tool for the job, session driving (the playwright loop) and autonomous exploration (tappexplore).