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/agent-sh/agentsys/claude-mdgit clone --depth 1 https://github.com/agent-sh/agentsysWhat 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.00360 | $0.00360 |
| Opus 5 | $0.00180 | $0.00180 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
agentsys 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- glidemq AGENTS.md — 86% identical, 13 lines differ
- glidemq CLAUDE.md — 86% identical, 13 lines differ
What it actually says
agentsys
A modular runtime and orchestration system for AI agents - works with Claude Code, OpenCode, and Codex CLI
Critical Rules
- Plain text output - No emojis, no ASCII art. Use
[OK],[ERROR],[WARN],[CRITICAL]for status markers. - No unnecessary files - Don't create summary files, plan files, audit files, or temp docs.
- Task is not done until tests pass - Every feature/fix must have quality tests.
- Create PRs for non-trivial changes - No direct pushes to main.
- Always run git hooks - Never bypass pre-commit or pre-push hooks.
- Use single dash for em-dashes - In prose, use
-(single dash with spaces), never--. - Report script failures before manual fallback - Never silently bypass broken tooling.
- Token efficiency - Save tokens over decorations.
Model Selection
| Model | When to Use |
|---|---|
| Opus | Complex reasoning, analysis, planning |
| Sonnet | Validation, pattern matching, most agents |
| Haiku | Mechanical execution, no judgment needed |
Core Priorities
- User DX (plugin users first)
- Worry-free automation
- Token efficiency
- Quality output
- Simplicity
Dev Commands
npm test # Run tests
npm run validate # All validators
References
- Part of the agentsys ecosystem
- https://agentskills.io
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 · 43 lines · 360 tokens per session scan A a15b7fc928e3
agentsys CLAUDE.md is an instructions file published in the GitHub repository agent-sh/agentsys (980 stars, last pushed 6d ago), licensed MIT. It adds 360 tokens to every session, about $0.0018 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-30.
Other instructions, from other repositories
LobsterAI AGENTS.md
AGENTS.md instructions for netease-youdao/LobsterAI, covering agents.md, instruction scope, project snapshot, cowork vs openclaw and commands.
hive AGENTS.md
AGENTS.md instructions for aden-hive/hive, covering repository guidelines, coding agent notes, multi-agent safety and change hygiene.
Upsonic CLAUDE.md
Claude Code instructions for Upsonic/Upsonic, covering claude.md, project overview, ai operational guides, default pre-work consultation and keep documents/ai/explanation/ in sync with code.
milady CLAUDE.md
Instructions for milady-ai/milady, covering milady — agent conventions, naming, cloud frontend visual review (required for any ui change), scope discipline and native over docker on linux x64.
milady AGENTS.md
Instructions for milady-ai/milady, covering milady — project codex guidance, cloud frontend visual review (required for any ui change), how to run, hard rules and elizaos naming.
ovo AGENTS.md
AGENTS.md instructions for qntx/ovo, a project described as: Agent behavior that compiles.