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/coderdeltalan/agent-rules-kit/agentsgit clone --depth 1 https://github.com/CoderDeltaLAN/agent-rules-kitWhat 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.00035 | $0.00035 |
| Opus 5 | $0.00017 | $0.00017 |
| Sonnet 5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
agent-rules-kit agents.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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-rules-kit agents.instructions.md — 100% identical, 0 lines differ
What it actually says
Agent Instructions
This fixture represents scoped GitHub instructions.
- Prefer small changes.
- Do not add secrets or private data.
- Verify changes before opening a pull request.
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 · 8 lines · 35 tokens per session scan A ea186fa687f8
agent-rules-kit agents.instructions.md is an instructions file published in the GitHub repository CoderDeltaLAN/agent-rules-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session, about $0.0002 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
anchor copilot-instructions.md
Instructions for peva3/anchor, covering github copilot instructions, required reading, critical rules, prohibited actions and project structure.
Harness-for-codex AGENTS.md
Instructions for ganimjeong/Harness-for-codex, covering codex harness instructions, commands, repository layout, operating principles and task loop.
anchor CLAUDE.md
Instructions for peva3/anchor: All project rules, patterns, and requirements are defined in AGENTS.md.
agents-md-doctor AGENTS.md
Instructions for ItsHege/agents-md-doctor, covering agents.md doctor public agent instructions, scope of this file, project goal, current baseline and working rules.
Harness-for-codex CLAUDE.md
Instructions for ganimjeong/Harness-for-codex, a project described as: Codex harness for consistent AI-assisted development workflows, including agent instructions, standard setup/check/test/eval scripts, CI, hooks, and documentation. | AI 기반 개발 작업을 일관되게 진행하기 위한 Codex 하네스입니다. 에이전트 지침, 표준 setup/check/test/eval 스크립트…
agentfit AGENTS.md
Instructions for kingkyylian/agentfit, covering agentfit agent instructions, setup, verification and scope.