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/sandeep-alluru/normsync/claude-mdgit clone --depth 1 https://github.com/sandeep-alluru/normsyncWrote 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/sandeep-alluru/normsync/claude-md)<a href="https://agentmods.dev/instructions/sandeep-alluru/normsync/claude-md"><img src="https://agentmods.dev/badge/instructions/sandeep-alluru/normsync/claude-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.00248 | $0.00248 |
| Opus 5 | $0.00124 | $0.00124 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
normsync CLAUDE.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.
What it actually says
normsync — Session Anchor
Research spec: ../tech-research/14-Gaming/social-contract-enforcement-engine-binding-multi-agent-n/README.md
One-liner: Emergent norm enforcement for multi-agent worlds — signed CRDT commitment ledger
Phase: backlog
Stack: Python, automerge-py (or py-crdt), cryptography, anthropic (Claude API)
Key decisions
- Key architectural separation: LLM decides WHAT norms exist; deterministic engine decides enforcement
Next step
Read the research spec, then design the signed commitment ledger schema.
MVP definition
pip install normsyncworks- Signed, versioned, append-only CRDT commitment ledger
- Tool-call interface: agents propose norms, accept norms, query active norms
- Deterministic enforcement engine (no LLM in the enforcement path)
- Demo: two NPC agents negotiate "don't attack allies" norm; third agent violates it; enforcement fires
- API:
normsync.propose(norm),normsync.accept(norm_id),normsync.enforce(action) - README with clear architecture diagram showing LLM vs deterministic boundary
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 · 23 lines · 248 tokens per session scan A aa5a4fba0884
normsync CLAUDE.md is an instructions file published in the GitHub repository sandeep-alluru/normsync (0 stars, last pushed 17d ago), licensed MIT. It adds 248 tokens to every session, about $0.0012 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
vnx-orchestration CLAUDE.md
Claude Code instructions for Vinix24/vnx-orchestration, covering vnx governance, mandatory report contract, dispatch lanes, path resolution and event streams.
tinysdlc AGENTS.md
Instructions for Minh-Tam-Solution/tinysdlc, covering setup activity, team communication, single teammate, multiple teammates (parallel fan-out) and shared context.
tinysdlc CLAUDE.md
Instructions for Minh-Tam-Solution/tinysdlc, covering claude ai project context — tinysdlc, sdlc compliance, documentation standards, when creating new documents and project overview.
AI-System-Design-Consultant CLAUDE.md
Claude Code instructions for deepanshu2711/AI-System-Design-Consultant, covering claude.md, what this is, running it, load-bearing typos — do not "fix" these paths and agent node pattern.
agent-eve CLAUDE.md
Instructions for shehryarsaroya/agent-eve, covering claude.md — agent eve (né the compact, then agent transfer), 0. 🚨 hard rules, 1. what this is, 2. doc map and 3. state of play (2026-07-26).
team-shinchan AGENTS.md
Instructions for seokan-jeong/team-shinchan, covering agents.md - team-shinchan agent map, layer architecture, agent registry, call flow and quick reference.