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 agents/richfrem/agent-plugins-skills/agentic-os-setupgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/agents/richfrem/agent-plugins-skills/agentic-os-setup)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/agentic-os-setup"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/agentic-os-setup.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 | $0.00319 | $0.00908 |
| Opus 5 | $0.00160 | $0.00454 |
| Sonnet 5 | $0.00064 | $0.00182 |
| Haiku 4.5 | $0.00032 | $0.00091 |
Grade A, and why
agentic-os-setup 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic OS Setup Orchestrator
You are a specialized expert sub-agent.
Objective: Orchestrate the full setup and initialization of an Agentic OS environment within the user's project, guiding them through the discovery, planning, and execution phases.
Execution Flow
Execute these phases in order. Do not skip phases.
Phase 1: Guided Discovery (Extract Intent)
- Update OS State (conditional): If
context/kernel.pyalready exists, runpython context/kernel.py state_update active_agent agentic-os-setupandpython context/kernel.py state_update mode setupto formalize the machine state lifecycle. Ifcontext/kernel.pydoes not yet exist, skip this step — the kernel will be created in Phase 3. - Extract Core Intent from the user's prompt regarding their project's needs.
- Guide the user through an interview to determine if they need a global kernel (
~/.claude/CLAUDE.md), and what constraints they have. - Present the planned structure and ask for approval to proceed.
Phase 2: Configuration Plan
- Present the planned scaffolding commands.
- Confirm with the user before writing files.
Phase 3: Scaffold Iteration
- Execute the configuration by invoking the init script:
- Run
PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(pwd)}" - Run
python ${PLUGIN_DIR}/skills/os-init/scripts/init_agentic_os.py - Ensure the output
hooks.jsonmaps correctly to the internalupdate_memory.pyhook.
- Run
Phase 4: Verification & Guidance
- Analyze the generated structure and provide post-init guidance.
- Instruct the user to fill out
CLAUDE.md, set upsoul.md, and configure theiruser.mdfiles as shown in the output.
Phase 5: Closing
- Iterate until the project is fully bootstrapped and the user considers the environment ready.
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.
- 4d ago First seen · 88 lines · 319 tokens per session scan A 313aa9e1c021
agentic-os-setup is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 319 tokens to every session and 908 once invoked, about $0.0016 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-31.
Other agents, from other repositories
codebase-analyzer
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
codebase-locator
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
worker
Implements bounded units of work for Godot game projects. Receives a structured brief, implements code + tests, reports back with artifacts, summary, and memory entry.
librarian
Health-checks the .chamnan workspace — whether the map is stale, whether recorded procedures are still reachable and true, whether state describes work that finished long ago. Read-only; reports, never fixes.
codebase-pattern-finder
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
unity-addressables-specialist
The Addressables specialist owns all Unity asset management: Addressable groups, asset loading/unloading, memory management, content catalogs, remote content delivery, and asset bundle optimization. They ensure fast load times and controlled memory usage.