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/pshkv/sint-protocol/agents-mdgit clone --depth 1 https://github.com/pshkv/sint-protocolWhat 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.02045 | $0.02045 |
| Opus 5 | $0.01022 | $0.01022 |
| Sonnet 5 | $0.00409 | $0.00409 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
sint-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 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.
This is a copy
95% identical to sint-protocol AGENTS.md — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SINT Protocol — AI Agent Guide
This file is optimized for AI agents (LLMs) working in this codebase. For human contributor guidance, see CONTRIBUTING.md. For implementation details and pitfalls, see CLAUDE.md.
What This Repo Does
SINT Protocol is a security enforcement layer that sits between AI agents and physical systems (robots, PLCs, drones, tool calls), ensuring every action is authorized via capability tokens, constrained to safe physical limits, and recorded in a tamper-evident audit log. It is a pnpm monorepo with 30 workspace members built on TypeScript 5.7 + Node.js 22.
Key Invariants (Never Violate These)
- Every authorization decision flows through
PolicyGateway.intercept()— no bridge or route handler makes authorization decisions directly - Tokens are attenuation-only:
scope(child) ⊆ scope(parent)— permissions only narrow, never expand (invariant I-T1) EvidenceLedgeris append-only and SHA-256 hash-chained — never modify or delete emitted events (invariant I-G3)- UUID v7 is required for
requestId—crypto.randomUUID()gives v4 and WILL fail schema validation. UsegenerateUUIDv7()from@sint/gate-capability-tokens - Physical constraints live in the token, not in config files — velocity, force, geofence are enforced cryptographically
- E-stop is unconditional —
estopevent transitions any non-terminal DFA state to ROLLEDBACK, bypassing all token checks (invariant I-G2)
Quick Orientation
Package Dependency Graph
@sint/core
↓
@sint/gate-capability-tokens @sint/persistence
↓ ↓
@sint/gate-evidence-ledger
↓
@sint/gate-policy-gateway
↓
@sint/bridge-* @sint/engine-* @sint/avatar
↓
@sint/gateway-server @sint/mcp
↓
@sint/conformance-tests @sint/dashboard
Workspace Layout
packages/core/ → Shared types, Zod schemas, tier constants, DFA states
packages/capability-tokens/ → Ed25519 token issuance, delegation, revocation
packages/policy-gateway/ → THE choke point: tiers, constraints, rate limiting, M-of-N
packages/evidence-ledger/ → SHA-256 hash-chained append-only audit log
packages/bridge-*/ → Protocol adapters (MCP, ROS2, A2A, IoT, OPC-UA, MAVLink, ...)
packages/engine-*/ → AI execution layer (System1, System2, HAL, capsule sandbox)
packages/avatar/ → Behavioral identity profiles, CSML-driven tier escalation
packages/persistence/ → Storage interfaces + in-memory implementations
packages/persistence-postgres/ → PostgreSQL adapters
packages/client/ → TypeScript HTTP client for the gateway API
packages/conformance-tests/ → Security regression suite (must pass on every PR)
apps/gateway-server/ → Hono HTTP API (port 3100)
apps/sint-mcp/ → Security-first multi-MCP proxy
apps/dashboard/ → Real-time approval dashboard
sdks/typescript/ → Zero-dependency public SDK
capsules/navigation/ → Reference capsule: waypoint navigation
capsules/inspection/ → Reference capsule: visual anomaly detection
capsules/pick-and-place/ → Reference capsule: gripper control
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 · 145 lines · 2,045 tokens per session scan A abd8a952361e
sint-protocol AGENTS.md is an instructions file published in the GitHub repository pshkv/sint-protocol (9 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 2,045 tokens to every session, about $0.0102 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to sint-protocol AGENTS.md, differing in 8 lines, and is treated as a copy.
Other instructions, from other repositories
agent-leash AGENTS.md
Instructions for tonydzi/agent-leash, covering agents.md — working in this repo, what this repo is, layout, how to verify a change and conventions — the claim discipline.
Doberman-Core AGENTS.md
Instructions for DobermanCore/Doberman-Core, covering claude.md — doberman operating manual, 0. on startup (every session), 1. what this repository is, 2. architecture & extension points and 3. prime directives (non-negotiable).
sint-protocol CLAUDE.md
Instructions for sint-ai/sint-protocol, covering sint protocol — agent guide, what is this?, quick commands, monorepo layout and architecture rules.
openfirma AGENTS.md
AGENTS.md instructions for Firma-AI/openfirma, covering agents.md, key commands, formatting, linting rules and api stability.
ardur AGENTS.md
Instructions for ArdurAI/ardur, covering ardur agent instructions, 0. first action in every new session, 1. what ardur is, and what it does not claim, 2. tl;dr commands and 3. architecture and trust boundaries.
ardur CLAUDE.md
Instructions for ArdurAI/ardur: This repository keeps a single, canonical set of agent instructions in AGENTS.md. This file exists only so that Claude Code loads them automatically; it deliberately holds no rules of its own, so that the two can never drift apart.