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/aantich/oneringai/claude-mdgit clone --depth 1 https://github.com/aantich/oneringaiWrote 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/aantich/oneringai/claude-md)<a href="https://agentmods.dev/instructions/aantich/oneringai/claude-md"><img src="https://agentmods.dev/badge/instructions/aantich/oneringai/claude-md.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.1 | $0.00220 | $0.00220 |
| Opus 5 | $0.00110 | $0.00110 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
oneringai 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 6d 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.
What it actually says
Claude Code instructions
AGENTS.md is the canonical OneRingAI guide for every coding agent.
Before planning or changing OneRingAI code, read ./AGENTS.md completely and
follow it. It contains the architecture invariants, integration recipes,
capability routing, documentation map, repository conventions, and validation
commands.
When OneRingAI is installed as a dependency rather than opened as its source repository, read:
node_modules/@everworker/oneringai/AGENTS.md
Do not maintain a separate Claude-specific copy of the API guidance here. This
small file intentionally delegates to AGENTS.md so Codex, Claude Code, and
custom agents use the same source of truth.
The essential invariant is:
named Connector -> Agent -> provider
|
+-> AgentContextNextGen plugins -> shared ToolManager
Use public package exports in consumer code, keep credentials in named
connectors, and verify uncertain APIs against API_REFERENCE.md, the relevant
specialist guide, and runnable examples.
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.
- 6d ago First seen · 32 lines · 220 tokens per session scan A 190b65c8e3b4
oneringai CLAUDE.md is an instructions file published in the GitHub repository aantich/oneringai (73 stars, last pushed yesterday), licensed MIT. It adds 220 tokens to every session, about $0.0011 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
AutoAgents AGENTS.md
Instructions for liquidos-ai/AutoAgents, covering autoagents repository guidelines, project structure & module organization, code quality, naming conventions and error handling.
deliberation CLAUDE.md
Claude Code instructions for antonbabenko/deliberation, covering claude.md, what this is, development commands, test plugin locally (loads from working directory) and run setup to test installation flow.
playbooks CLAUDE.md
Instructions for playbooks-ai/playbooks, covering claude.md, project overview, core architecture, framework components and key architectural insights.
llm-cli-gateway CLAUDE.md
Claude Code instructions for verivus-oss/llm-cli-gateway, covering claude.md, repository overview, development commands, build and test and run all tests.
grok-faf-mcp AGENTS.md
AGENTS.md instructions for Wolfe-Jam/grok-faf-mcp, covering agents.md — grok-faf-mcp, project context, stack and human context.
grok-faf-mcp CLAUDE.md
Claude Code instructions for Wolfe-Jam/grok-faf-mcp, covering claude.md — grok-faf-mcp, what this is, stack and context.