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/dipakkr/agentsync/claude-mdgit clone --depth 1 https://github.com/dipakkr/agentsyncWhat 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.00056 | $0.00056 |
| Opus 5 | $0.00028 | $0.00028 |
| Sonnet 5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
agentsync 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 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
See AGENTS.md for how to work on this repo through the AgentSync hub (identify yourself, claim tasks, check conflicts before pushing).
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 · 4 lines · 56 tokens per session scan A b1be000f683e
agentsync CLAUDE.md is an instructions file published in the GitHub repository dipakkr/agentsync (0 stars, last pushed 24d ago), licensed MIT. It adds 56 tokens to every session, about $0.0003 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
martin-loop AGENTS.md
Instructions for Keesan12/martin-loop, covering martinloop agent operating rules, repository authority, mandatory internal-first sequence, prohibited actions and required internal health proof.
Kiln AGENTS.md
AGENTS.md instructions for Kiln-AI/Kiln, covering project overview, project goals, tech stack, agent tools and agent prompts.
liveblocks AGENTS.md
AGENTS.md instructions for liveblocks/liveblocks, covering project structure, bash commands, code style, dependencies and code quality.
open-tag AGENTS.md
Instructions for fancyboi999/open-tag, covering open-tag — guide for ai coding agents, this file is a map, not a manual, conventions, parallel development (worktrees) and isolated dev e2e (on demand).
sample-well-architected-skills-and-steering copilot-instructions.md
Copilot instructions for aws-samples/sample-well-architected-skills-and-steering, covering well-architected framework, role, when to apply, pillars and design principles.
cli AGENTS.md
AGENTS.md instructions for jumbocontext/cli, covering agents.md and instructions for agents on how to collaborate with jumbo.