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 aiocean/claude-plugins --skill aio-mapgit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-map)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-map"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-map/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/aiocean/claude-plugins/aio-map"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-map.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.00048 | $0.00671 |
| Opus 5.5 | $0.00019 | $0.00268 |
| Sonnet 5.5 | $0.00010 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
aio-map 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 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.
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
Map — Structural Analysis
Environment
- GitNexus: !
npx gitnexus status 2>/dev/null && echo "AVAILABLE" || echo "NOT INSTALLED"
Build a dependency and symbol map for files identified by /discover. Uses GitNexus for overview, LSP for precision.
Prerequisites
- GitNexus indexed (
npx gitnexus analyze) — verify withnpx gitnexus status - LSP servers running (TypeScript/Rust)
Workflow
Step 1: Symbol inventory (GitNexus) — run in parallel
For each relevant file from discovery, use the GitNexus MCP context tool:
context(file)
Fast overview of symbols and dependencies without reading the full file.
Step 2: File dependencies (GitNexus) — run in parallel
context(file) → imports and dependents for the file
impact(file) → what does changing this file affect?
Note: GitNexus tracks TS imports well. For Rust modules, fall back to LSP.
Step 3: Precise references (LSP)
For key functions that will be modified:
lsp_find_references(file, line, character) → all call sites
lsp_goto_definition(file, line, character) → where defined
lsp_hover(file, line, character) → type info
LSP is authoritative — always trust LSP over GitNexus for caller/callee data.
Step 4: Output structural map
## Map: [feature area]
### File: `path/file.ts` (N functions)
**Key functions:** fn1, fn2, fn3
**Imports:** file-a.ts, file-b.ts
**Imported by:** file-c.tsx, file-d.tsx
**References:**
- `fn1` called from: file-c.tsx:42, file-d.tsx:88
### Dependency Graph
file-a → file-b → file-c
↘ file-d
### Blast Radius
Changing `fn1` affects: [list of downstream files]
### Next Step
Run `/plan` to synthesize into implementation plan.
Tool priority
- GitNexus
context— fast file overview (always works) - GitNexus
impact— blast radius / downstream effects - LSP
lsp_find_references— precise function-level tracing - LSP
lsp_hover— type information when needed
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 First seen · 86 lines · 48 tokens per session scan A 9234ff1b270b
aio-map is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 671 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
code-review
Review code changes for concrete defects.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
eval-hooks
Audit Claude Code and Codex hooks for validity, safety, and correctness across settings.json, hooks.json, config.toml, plugin, and skill or agent frontmatter hooks. Resolves each command, checks event names, handler types, matchers, exit-code and JSON decision strategy, and timeouts against each host's documented…
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-skills
Audit a project or library of skills for metadata, trigger boundaries, workflow completion criteria, local resource closure, instruction economy, tool scope, effort, and routing evidence. Use before shipping skills, after importing a skill collection, or when a skill triggers too often or not at all.