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 skills/aiocean/claude-plugins/aio-plannpx skills add aiocean/claude-plugins --skill aio-plangit 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-plan)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-plan"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-plan.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.00042 | $0.01125 |
| Opus 5 | $0.00021 | $0.00562 |
| Sonnet 5 | $0.00008 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
aio-plan 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — Implementation Planning
Environment
- GitNexus: !
npx gitnexus status 2>/dev/null && echo "AVAILABLE" || echo "NOT INSTALLED"
Synthesize discovery and mapping results into a concrete, actionable implementation plan.
Prerequisites
- Run
/discoverand/mapfirst (or have equivalent understanding) - GitNexus indexed (
npx gitnexus analyze) for convention/duplication checks
Workflow
Step 1: Duplication check (GitNexus)
Search if similar features already exist using the GitNexus MCP query tool:
query("similar feature or pattern")
Prevents building what already exists.
Step 2: Convention check (GitNexus)
Search for existing patterns to follow:
query("how are [similar things] implemented")
Examples: "tauri command structure", "hook cleanup pattern", "error handling in rust"
Step 3: Context enrichment (GitNexus)
For each file you plan to modify, get full context:
context(file)
This reveals dependencies, dependents, and all symbols — helps identify:
- Functions that will be affected by your changes
- Files that import the file you're changing (blast radius)
- Existing symbols you can reuse instead of creating new ones
For the most critical change, check impact:
impact(file)
Step 4: Write the plan
## Plan: [Feature/Fix Name]
### Goal
[One sentence: what and why]
### Discovery Summary
[Key findings from /discover]
### Approach
[High-level strategy: which layer handles what]
### Changes
#### 1. `file path` — [what changes]
- [ ] Add/modify function `X` to do Y
- [ ] Update type `Z`
- Reason: [why this file]
#### 2. `file path` — [what changes]
- [ ] ...
### Risks
- **[Risk]**: [Mitigation]
### Convention Check
- Follows: [existing pattern found]
- Deviates: [if any, with justification]
### NOT Doing
[Explicitly list out-of-scope items]
Step 5: Create baseline
Run /aio-snapshot before starting implementation.
Step 6: Execution handoff
After the plan is approved, choose an execution strategy:
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 · 146 lines · 42 tokens per session scan A 49155defb189
aio-plan is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,125 once invoked, about $0.0002 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 skills, from other repositories
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
source-command-ccguide-daily
Daily update check — official Anthropic docs diff + guide/CC releases digest.
source-command-ccguide-diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
source-command-changelog
View recent CHANGELOG entries.
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…
go-dependency-audit
Go dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply…