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/agentcrdt/copilot-instructionsgit clone --depth 1 https://github.com/sandeep-alluru/agentcrdtWrote 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/agentcrdt/copilot-instructions)<a href="https://agentmods.dev/instructions/sandeep-alluru/agentcrdt/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sandeep-alluru/agentcrdt/copilot-instructions.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.00250 | $0.00250 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
agentcrdt copilot-instructions.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
83% identical to groundcrew copilot-instructions.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.
What it actually says
GitHub Copilot Instructions — agentcrdt
agentcrdt: Semantic-causal CRDT for agent-mutable world state
Module map
src/agentcrdt/
├── # TODO: fill in after implementation
Key invariants
- TODO: document invariants
Code style
- Python 3.10+, type-annotated, mypy strict mode
- Ruff lint rules: E W F I UP B S N SIM RUF PT; ignore S101 (assert in tests), N806
- No
print()in library code — userich.console.Console - All public classes and functions must have docstrings
- Tests use
pytest; CLI tests useclick.testing.CliRunner
Adding a new output format
- Add
to_<format>(result) -> strinreport.py - Add format name to
--formatchoices incli.py - Add tests
Adding a new adapter / integration
- Create
src/agentcrdt/instrument_<framework>.py - Export from
__init__.py, add to__all__alphabetically - Add tests
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 · 35 lines · 250 tokens per session scan A 9f43696bdfd7
agentcrdt copilot-instructions.md is an instructions file published in the GitHub repository sandeep-alluru/agentcrdt (0 stars, last pushed 17d ago), licensed MIT. It adds 250 tokens to every session, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to groundcrew copilot-instructions.md, differing in 8 lines, and is treated as a copy.
Other instructions, from other repositories
yorkie CLAUDE.md
Claude Code instructions for yorkie-team/yorkie, covering yorkie — crdt-based collaboration server, commands, integration test environment, commit messages and key architecture.
mesh-llm pr.instructions.md
Instructions for Mesh-LLM/mesh-llm: When doing work on pull requests, do not re-title the PR to reflect the latest changes, and do not edit the PR's description with the most recent update. Instead, use inline comments to summarize your work and the changes that were made ONLY IF THERE IS NON-OBVIOUS INFORMATION THAT…
yorkie-js-sdk CLAUDE.md
Claude Code instructions for yorkie-team/yorkie-js-sdk, covering yorkie javascript sdk, development commands, tests require a running yorkie server, after making changes and project docs.
mesh-llm AGENTS.md
AGENTS.md instructions for Mesh-LLM/mesh-llm, covering agent notes, repo overview, key docs, public website and building.
omnidraw AGENTS.md
Instructions for omnidraw/omnidraw, covering omnidraw repository guide, architecture authorities, public package boundaries, @omnidraw/canvas-contract and @omnidraw/canvas.
OpenGameAgent AGENTS.md
AGENTS.md instructions for EricSun0218/OpenGameAgent, covering coding agent guide, objective, repository map, non-negotiable boundaries and first commands.