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/yaalalabs/agent-kernel/claude-mdgit clone --depth 1 https://github.com/yaalalabs/agent-kernelWhat 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.00122 | $0.00122 |
| Opus 5 | $0.00061 | $0.00061 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
agent-kernel 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.
What it actually says
CLAUDE.md
See AGENTS.md — it has the full guide for working on this repo (repo map, setup/lint/test commands, the dev-skills-vs-bundled-skills distinction, and conventions). Read it before making changes.
Claude Code specifically: the dev skills under .agents/skills/ (ak-dev-architecture,
ak-dev-testing-conventions, ak-dev-new-*, etc.) are already registered — invoke them via the Skill tool
instead of re-deriving that context from scratch.
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 · 9 lines · 122 tokens per session scan A 041612d049a1
agent-kernel CLAUDE.md is an instructions file published in the GitHub repository yaalalabs/agent-kernel (145 stars, last pushed 5d ago), licensed Apache-2.0. It adds 122 tokens to every session, about $0.0006 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
awesome-kubernetes CLAUDE.md
Instructions for nubenetes/awesome-kubernetes, covering claude.md — nubenetes project instructions for claude code, git workflow: gitflow, branches, release process (mandatory for all releases) and versioning.
awesome-kubernetes GEMINI.md
Instructions for nubenetes/awesome-kubernetes, covering 🧠 core mandates, 🛠️ structural evolution & navigation, 📊 mermaid diagram best practices, 🛡️ repository policies & branch protection and 📝 readme synchronization & maintenance protocols.
aurora AGENTS.md
Instructions for Arvo-AI/aurora, covering aurora - agent guidelines, commands, docker deployments, architecture and secrets management (vault).
drawio-ai-kit AGENTS.md
Instructions for sparklabx/drawio-ai-kit, covering repository guidelines, tech stack & runtime and code conventions & common patterns.
adk CLAUDE.md
Instructions for inference-gateway/adk, covering claude.md, what this repo is, commands, architecture and server (server/).
IsaacAutomator AGENTS.md
Instructions for isaac-sim/IsaacAutomator, covering isaac automator - agent instructions, operator quickstart (the short version), rules for agents (read before acting) and map.