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/agent-receipts/obsigna/gogit clone --depth 1 https://github.com/agent-receipts/obsignaWhat 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.00127 | $0.00127 |
| Opus 5 | $0.00063 | $0.00063 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
obsigna go.instructions.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 2d 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
Go review guidelines
- Pure Go SQLite via modernc.org/sqlite — flag any CGO dependencies.
- Errors must be wrapped with context (
fmt.Errorf("operation: %w", err)). Flag bare error returns. - Tests sit alongside source files as
*_test.go. Flag test files in separate directories. - Run
go vet ./...before committing. - The mcp-proxy depends on sdk/go via a
replacedirective — changes to sdk/go should trigger mcp-proxy test verification.
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.
- 2d ago First seen · 14 lines · 127 tokens per session scan A 51521eb546b1
obsigna go.instructions.md is an instructions file published in the GitHub repository agent-receipts/obsigna (20 stars, last pushed 3d ago), licensed Apache-2.0. It adds 127 tokens to every session, about $0.0006 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-30.
Other instructions, from other repositories
warrant AGENTS.md
Instructions for s0fractal/warrant, covering agent & contributor conduct (governance-critical), hard rules, the human's role and precedent (why this file exists).
VCVio AGENTS.md
Instructions for Verified-zkEVM/VCVio, covering vcvio — ai agent guide, fast start, attribution, headers, and docstrings, module scopes and what this project is.
jentic-one GEMINI.md
Instructions for jentic/jentic-one: Otherwise, read AGENTS.md — this repo's canonical agent guidance.
hig-doctor AGENTS.md
AGENTS.md instructions for raintree-technology/hig-doctor: HIG Doctor combines open-source audit tooling with an attributed snapshot of Apple's Human Interface Guidelines.
agent-passport-system AGENTS.md
Instructions for aeoess/agent-passport-system, covering agents.md, dev environment, test before you ship, pr instructions and code style.
briefloop AGENTS.md
Instructions for Stahl-G/briefloop, covering agents.md, purpose, instruction scope, environment separation and context mode.