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/pythongit 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.00113 | $0.00113 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
obsigna python.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 yesterday.
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
Python SDK review guidelines
- Prefer
from __future__ import annotationsin new or heavily-typed modules. - Pydantic v2 for receipt models, frozen dataclasses for simple types.
- Use
TYPE_CHECKINGguards for type-only imports. - Ruff for lint and format (line-length 88). Flag lines exceeding this.
- Tests mirror
src/structure undertests/. Flag tests placed elsewhere. - Output must be byte-identical to the TypeScript SDK.
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.
- yesterday First seen · 13 lines · 113 tokens per session scan A bb9a2b72545b
obsigna python.instructions.md is an instructions file published in the GitHub repository agent-receipts/obsigna (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 113 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).
chatgpt-cli CLAUDE.md
Instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
Sighthound AGENTS.md
Instructions for Corgea/Sighthound, covering claude, commands, python / django test naming and agent skill.
jentic-one GEMINI.md
Instructions for jentic/jentic-one: Otherwise, read AGENTS.md — this repo's canonical agent guidance.
openings-mcp AGENTS.md
Instructions for amikai/openings-mcp, a project described as: 💼 One MCP server to search job boards and company career sites.
uspto-cli CLAUDE.md
Instructions for smcronin/uspto-cli, covering uspto cli - project guide, what this is, architecture, key conventions and building.