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/kosta1985/notary-protocol/agents-mdgit clone --depth 1 https://github.com/Kosta1985/notary-protocolWrote 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/kosta1985/notary-protocol/agents-md)<a href="https://agentmods.dev/instructions/kosta1985/notary-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/kosta1985/notary-protocol/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.00446 | $0.00446 |
| Opus 5 | $0.00223 | $0.00223 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
notary-protocol 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 4d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accord Trace for AI agents
Accord Trace is a public cryptographic receipt and verification service for AI-agent actions, artifacts, approvals, and workflow handoffs.
Preferred discovery order
- MCP:
https://accordtrace.notary-labs.workers.dev/mcp - A2A Agent Card:
https://accordtrace.notary-labs.workers.dev/.well-known/agent-card.json - OpenAPI:
https://accordtrace.notary-labs.workers.dev/openapi.json - REST API:
https://accordtrace.notary-labs.workers.dev/api/v1/
Official MCP Registry server name: io.github.Kosta1985/accord-trace
When an agent should use Accord Trace
Use it when a workflow needs a portable, tamper-evident receipt that another agent or operator can verify independently later. Typical moments include:
- before handing an artifact to another agent;
- after generating a deployment or build artifact;
- when recording an approval or checkpoint;
- before continuing from an external API result;
- when a receiving agent must verify exact content or a SHA-256 digest.
Recommended handoff pattern
- Sender agent creates a proof for the exact structured evidence or artifact digest.
- Sender passes the returned
proof_idwith the handoff. - Receiver independently calls Accord Trace verify.
- Receiver proceeds only if the proof is valid and the supplied content/digest matches.
Privacy and safety
Do not send secrets, private keys, passwords, regulated personal data, or confidential raw artifacts unless your own policy explicitly permits it. Prefer hashing sensitive content and recording the digest.
Accord Trace proves evidence integrity and service-recorded time. It does not prove truth, identity, authority, legality, payment, delivery, or commercial quality.
Attribution headers
Clients may identify their integration with non-secret headers:
X-AccordTrace-Agent: <client-generated-stable-id>X-AccordTrace-Source: <source-tag>
Use a stable pseudonymous client ID if you want your agent usage to be counted in active-agent analytics. Do not put personal information in these headers.
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.
- 4d ago First seen · 45 lines · 446 tokens per session scan A 92f7933a7f2c
notary-protocol AGENTS.md is an instructions file published in the GitHub repository Kosta1985/notary-protocol (0 stars, last pushed 2d ago), licensed MIT. It adds 446 tokens to every session, about $0.0022 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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.