What is notary-protocol AGENTS.md?

Repository instructions that tell coding agents how to use Accord Trace, a service that creates verifiable receipts for actions, files, approvals, and handoffs.

Use them when handing over files, recording approvals, checking build or deployment artifacts, or verifying results from an external service.

They give agents a consistent way to record and verify what happened, helping prevent confusion or unnoticed changes when work moves between agents or people.

How Kosta1985/notary-protocol configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to Kosta1985/notary-protocol. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Kosta1985/notary-protocol/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Kosta1985/notary-protocol

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/kosta1985/notary-protocol/agents-md/github.svg)](https://agentmods.dev/instructions/kosta1985/notary-protocol/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/kosta1985/notary-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/kosta1985/notary-protocol/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,237 This file is loaded in full into every session.

When invoked 1,237 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01237	$0.01237
Opus 5.5	$0.00495	$0.00495
Sonnet 5.5	$0.00247	$0.00247
Haiku 4.5	$0.00124	$0.00124

Measured 2mo ago against content hash 6ab887d39678, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

AGENTS.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 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, verification, defensive security, reputation-evidence, and least-privilege authorization service for AI-agent actions, artifacts, approvals, workflow handoffs, Agent Passports, bilateral work/payment attestations, and capability leases.

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
AI catalog: https://accordtrace.notary-labs.workers.dev/.well-known/ai-catalog.json
OpenAPI: https://accordtrace.notary-labs.workers.dev/openapi.json
REST API: https://accordtrace.notary-labs.workers.dev/api/v1/
Agent Security capabilities: https://accordtrace.notary-labs.workers.dev/api/v1/security/capabilities
Reputation Evidence capabilities: https://accordtrace.notary-labs.workers.dev/api/v1/trust/capabilities
Capability Gateway: https://accordtrace.notary-labs.workers.dev/api/v1/gateway/capabilities

Official MCP Registry server name: io.github.Kosta1985/accord-trace

When an agent should use Accord Trace

Use it when a workflow needs portable, tamper-evident evidence or a cryptographic authorization decision that another agent, operator, or enforcement layer can verify and act on. 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;
when an autonomous agent needs a cryptographic Passport tied to an Ed25519 key;
when an authorized operator wants signed security signals or passive canaries for their own agent infrastructure;
when provider and requester agents want bilateral evidence that a proof-bound marketplace delivery was accepted or disputed;
when payer and payee agents want to record matching signed payment claims without giving AccordTrace custody of funds;
before an enforcement layer lets an agent invoke a protected tool, API, MCP server, or network origin under a short-lived capability lease.

Read the full file on GitHub · 94 lines

Changes

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.

2mo ago Changed · +49 lines · +791 tokens per session 6ab887d39678
2mo ago First seen · 45 lines · 446 tokens per session scan A 92f7933a7f2c

Subscribe to this mod's changes

notary-protocol AGENTS.md is an instructions file published in the GitHub repository Kosta1985/notary-protocol (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,237 tokens to every session, about $0.0049 per session on Opus 5.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.

notary-protocol AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
notary-protocol AGENTS.mdKosta1985/notary-protocol	Instructions file	0	2mo ago	MIT	A	1,237	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

notary-protocol: Instructions file for Codex