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/sublang-ai/cligent/agents-mdgit clone --depth 1 https://github.com/sublang-ai/cligentWhat 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.00292 | $0.00292 |
| Opus 5 | $0.00146 | $0.00146 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
cligent 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cligent CLAUDE.md — 92% identical, 5 lines differ
What it actually says
AGENTS
Specs (Source of Truth)
- Canonical specs live in @specs/. Start with @specs/map.md for a quick-reference index and @specs/meta.md for the spec format; spec packages live in @specs/packages.
- Before making changes or suggestions in an area that has a spec, read the relevant spec file(s) first and follow them.
- Whenever your changes involve any spec, or you make a decision worth recording, keep the specs in sync — don't let them drift.
- Resolve conflicts spec-first, then iterate freely: an intended change that conflicts with existing spec items is resolved in the specs — or dropped — before coding against it; implementing first to explore an approach is fine, and implementation lessons update this intent's specs, but no intent completes until its specs and code agree.
- Keep specs lawful per @specs/meta.md — the law itself, not this summary: complete and exact (meta-34), minimal (meta-23), one requirement per item (meta-29), cohesive packages for a shared intent (meta-13), sections per meta-30, relationships and test evidence only as inline citations (meta-14, meta-16, meta-20), integration/system tests only (meta-21, meta-32).
- Run
spex lintto check structure, item IDs, and citations after editing specs; never add trace lines to satisfy an older checker.
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 · 12 lines · 292 tokens per session scan A feb325328901
cligent AGENTS.md is an instructions file published in the GitHub repository sublang-ai/cligent (52 stars, last pushed 4d ago), licensed Apache-2.0. It adds 292 tokens to every session, about $0.0015 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
obsidian-mind CLAUDE.md
Claude Code instructions for breferrari/obsidian-mind, covering obsidian mind, skills & capabilities, custom slash commands, vault structure and obsidian cli.
TokenTracker CLAUDE.md
Claude Code instructions for xiufengsun/TokenTracker, covering claude.md, project shape, frequently used commands, what's where and load-bearing conventions.
obsidian-mind AGENTS.md
AGENTS.md instructions for breferrari/obsidian-mind, covering obsidian mind, hooks, commands, memory and reaching this vault from another repo.
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
neo4j-skills AGENTS.md
Instructions for neo4j-contrib/neo4j-skills, covering writing skills for this repository, language style — write for agents, not humans, six design principles, skill.md spec (agentskills.io) and frontmatter.
ox AGENTS.md
Instructions for sageox/ox, covering human attention is the scarcest resource, what is ox?, quick start, terminology and required reviews.