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/elbwalker/walkeros/claude-mdgit clone --depth 1 https://github.com/elbwalker/walkerOSWhat 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.00093 | $0.00093 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00019 | $0.00019 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
walkerOS 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 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.
What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Important: Use AGENT.md
The actual instructions and guidelines for working with the walkerOS codebase are maintained in:
Read @AGENT.md
Refer to AGENT.md for all relevant instructions. The AGENT.md file contains the comprehensive documentation that should be followed when working with this codebase.
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 · 16 lines · 93 tokens per session scan A 65d2e73f700d
walkerOS CLAUDE.md is an instructions file published in the GitHub repository elbwalker/walkerOS (343 stars, last pushed 6d ago), licensed MIT. It adds 93 tokens to every session, about $0.0005 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
magicui AGENTS.md
Instructions for magicuidesign/magicui, covering project context, key principles, before writing code, rules and accessibility (a11y).
core CLAUDE.md
Claude Code instructions for module-federation/core, covering claude task parallelization & development guidelines, core principles, maximum parallelization strategy, universal parallel task patterns and for any codebase task.
orval AGENTS.md
AGENTS.md instructions for orval-labs/orval, covering using vite+, the unified toolchain for the web, built-in commands vs scripts, tool versions and review checklist.
ui-components AGENTS.md
Instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).
deepseek-pp AGENTS.md
Instructions for zhu1090093659/deepseek-pp, covering deepseek++ project agent instructions, scope, product context, truth sources and collaboration rules.
webiny-js CLAUDE.md
Claude Code instructions for webiny/webiny-js, covering context, claude project guidelines, reading code, development commands and install dependencies (suppress all output – it's noise).