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/orin-dx/agent-plugins/agents-mdgit clone --depth 1 https://github.com/orin-dx/agent-pluginsWhat 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.00913 | $0.00913 |
| Opus 5 | $0.00456 | $0.00456 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
agent-plugins 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orin DX AI Agent & Skill Specification (AGENTS.md)
This guide defines the top-level repository guidelines for AI coding agents (Claude Code, AGY, Cursor, Copilot, Codex) working on or utilizing orin-dx/agent-plugins.
1. Authoritative Sources
All hard rules for plugin and agent authoring live in one place:
shared/constitution.md: EARS-format authoritative constraints. The fence all plugin development must stay inside. Read this first and last.shared/agent-best-practices.md: Principles behind the constitution, explained with examples. Authoring-time only — never loaded by agents at runtime.shared/debugging-laws.md: Core proof laws, read-only investigation rules, Red-to-Green verification standards.shared/references/modern-cli-tools.md: Global preference directive for modern CLI tools (bat,zoxide,ripgrep,fd,eza,delta,jq,fzf,gh).
2. Directory Layout Standard
plugins/<plugin-id>/
├── plugin.json <-- Plugin Manifest (id, version, skills, agents)
├── README.md <-- Purpose, trigger phrases, agent table, install
├── CHANGELOG.md <-- Semver history
├── skills/
│ └── <plugin-id>/
│ └── SKILL.md <-- Skill definition (dispatch matrix, pipeline)
└── agents/
├── recon.md <-- haiku/low — deterministic enumeration
├── scanner.md <-- sonnet/med — pattern matching
├── adversary.md <-- sonnet/med — adversarial verification
└── exit-gate.md <-- opus/high — binding judgment
A plugin defaults to one skill directory named after the plugin id, as above. IF the plugin's scope covers several genuinely independent, heterogeneous intents on the same artifact — not a linear pipeline invoked as one flow — skills/<plugin-id>/ may split into skills/<skill-name>/SKILL.md per skill instead. courier, scribe, weaver, and mason are examples. The skill-routing key is the directory name, not the frontmatter name: field. A new skill name defaults to a single lifecycle-stage word; only go to a specific compound name (audit-spec, not scribe-audit) when the bare word is ambiguous or collides with another plugin's existing skill name. See shared/constitution.md's Plugin Structure and Skill Names sections.
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.
- 2d ago First seen · 51 lines · 913 tokens per session scan A 49d19c4c2075
agent-plugins AGENTS.md is an instructions file published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 5d ago), licensed MIT. It adds 913 tokens to every session, about $0.0046 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
vibeguard AGENTS.md
Instructions for majiayu000/vibeguard, covering agent instructions, scope, start here, core rules and delivery policy.
agent-skills AGENTS.md
Instructions for helderberto/agent-skills, covering agents.md, repository overview, project structure, integration model and opencode integration.
free-ai-gateway AGENTS.md
Instructions for zaber-dev/free-ai-gateway, covering 🤖 free-ai gateway - agentic development guidelines, 🏛️ monorepo architecture & package boundaries, 🛑 strict architectural rules for agents, 💻 essential developer commands and build all packages across monorepo.
agent-plugins-spec AGENTS.md
AGENTS.md instructions for agentplugins/agent-plugins-spec, covering agent instructions, purpose and authority, design posture, portability boundaries and editorial discipline.
cli-code-skills CLAUDE.md
Instructions for Destynova2/cli-code-skills, covering claude.md — cli-code-skills, skills installation, validation, evaluations and current skills (36).
aiworkspace AGENTS.md
Instructions for a-tokyo/aiworkspace, covering ai workspace, structure, key commands, conventions and code quality.