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 skills add rexleimo/aios --skill aios-codemap-opsgit clone --depth 1 https://github.com/rexleimo/aiosWrote 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/skills/rexleimo/aios/aios-codemap-ops)<a href="https://agentmods.dev/skills/rexleimo/aios/aios-codemap-ops"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/aios-codemap-ops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rexleimo/aios/aios-codemap-ops"><img src="https://agentmods.dev/badge/skills/rexleimo/aios/aios-codemap-ops.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.01071 |
| Opus 5.5 | $0.00024 | $0.00428 |
| Sonnet 5.5 | $0.00012 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade B, and why
aios-codemap-ops scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| Codex | `~/.codex/config.toml` (`[mcp_servers.code-review-graph]`) | How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRG Tool Quick Reference
Install/Doctor Targets
aios internal codemap install --client all should make CRG available to the AIOS-supported clients:
| Client | Config written |
|---|---|
| Codex | ~/.codex/config.toml ([mcp_servers.code-review-graph]) |
| Claude Code | <project>/.mcp.json |
| Gemini CLI | <project>/.gemini/settings.json |
| OpenCode | ~/.config/opencode/opencode.json plus plugins/crg-plugin.ts |
If a client cannot see CRG tools, run aios internal codemap doctor --fix --client <client> from the target project, then restart that client.
Structured-plan context candidates
When you know a structured-plan task's implementation target, do not ask a human to hand-author every supporting context reference.
- Call AIOS MCP
aios_plan_taskwithaction: "propose_context", the activetask_id, and workspace-relativetargetswhen the task has no targets yet. - AIOS derives a durable proposal from the target plus CRG callers, callees/imports, and tests. This proposal is reviewable only; it does not alter
.aios/planning/active.json. - Present the refs and reasons to the human. Ask a human to activate all candidates with
aios plan task <id> --confirm-context-candidates, or select a subset by repeating--candidate-ref <ref>; this is an explicit process step, not an identity/authentication boundary. - Only after confirmation may you say that the task has active execution context or invoke context-dependent orchestration.
query_graph patterns
| Pattern | Returns |
|---|---|
callers_of |
Functions that call the target |
callees_of |
Functions called by the target |
imports_of |
Imports from a file/module |
importers_of |
Files that import a file/module |
children_of |
Nodes contained in a file/class |
tests_for |
Tests covering the target |
inheritors_of |
Classes inheriting from target |
file_summary |
All nodes in a file |
refactor_tool modes
| Mode | Action |
|---|---|
rename |
Preview rename across all locations |
dead_code |
Find unreferenced symbols |
suggest |
Community-driven refactoring suggestions |
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.
- 1mo ago Changed 5f9986a47078
- 1mo ago Changed 40c751bf3556
- 1mo ago Changed 24ffe4ca8ffc
- 1mo ago First seen · 97 lines · 60 tokens per session scan B 2377e2e71ae2
aios-codemap-ops is a skill published in the GitHub repository rexleimo/aios (61 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,071 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
checking-code-quality
Checks code quality metrics including complexity, duplication, naming conventions, and function length. Use when running quality gates, reviewing code smells, or checking lint rules. Automatically triggered on complex modules or post-refactor.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
verifying-modules
Scans directory structure, detects missing documentation, and verifies code-doc synchronization. Use when checking module completeness, README presence, or DESIGN.md alignment. Automatically triggered after creating new modules.
orchestrating-adversarial-reviews
Multi-agent adversarial-verification orchestration for high-confidence conclusions. Fan-out finders, then verify every finding through a three-prism panel (exploitability / correctness / refutation) that defaults to disbelief, gate fixes behind load-bearing proof tests that catch agents who falsely claim "done/fixed"…
task-workflow
Shared implementation workflow for task-based skills, with profile-check sites wrapped in Jinja conditionals.