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/sma1lboy/rove/hownpx skills add Sma1lboy/rove --skill howgit clone --depth 1 https://github.com/Sma1lboy/roveWrote 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/sma1lboy/rove/how)<a href="https://agentmods.dev/skills/sma1lboy/rove/how"><img src="https://agentmods.dev/badge/skills/sma1lboy/rove/how.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.00064 | $0.01602 |
| Opus 5 | $0.00032 | $0.00801 |
| Sonnet 5 | $0.00013 | $0.00320 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
how 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.
This is a copy
86% identical to how — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How
Explore the codebase to answer "how does X work?" questions. Produce clear architectural explanations at the level of a senior engineer onboarding onto a subsystem. Enough to build a working mental model, not annotated source code.
Two modes:
- Explain (default). Explore the codebase and produce a clear explanation
- Critique. Explain first, then spawn multiple models to independently identify architectural issues
Explain Mode
Step 1. Understand the Question and Assess Complexity
Parse what the user is asking about:
- "How does the rate limiter work?", a subsystem
- "How do we handle billing for on-demand usage?", a feature flow
- "How is the auth service structured?", an architectural overview
- "Walk me through what happens when a user submits a form", a runtime trace
Identify the scope. If ambiguous, state your best-guess interpretation before exploring. Don't ask. Let the user redirect if you're off.
Assess complexity to decide the approach:
- Simple (a single module, a small utility, a narrow question like "how does function X work"): skip explorer agents; the explainer explores and explains in a single pass. Go to Step 2b.
- Complex (a subsystem spanning multiple files/services, a cross-cutting feature, a full architectural overview): spawn parallel explorer agents first, then hand off to the explainer. Go to Step 2a.
When in doubt, lean simple. You can always spawn explorers if the explainer hits a wall.
Step 2a. Explore (complex questions only)
Decompose the question into 2-4 parallel exploration angles, each a distinct slice of the subsystem so explorers don't duplicate work. Example split for "how does the rate limiter work?":
- Explorer 1: data model and state management
- Explorer 2: request path and enforcement
- Explorer 3: configuration and metrics infrastructure
The right decomposition depends on the question. Use your judgment. Narrow questions: 2 explorers is fine. Broad subsystems: up to 4.
Spawn all explorers in a single message:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 135 lines · 64 tokens per session scan A fe503e7a9b2a
how is a skill published in the GitHub repository Sma1lboy/rove (115 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,602 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to how, differing in 25 lines, and is treated as a copy.
Other skills, from other repositories
ai-change-impact
Measure what a change to an AI coding setup actually saved, in dollars. Compares recorded before/after usage from the AI Insights MCP server — either two specific sessions by id, or everything in one period against another — and attributes the cost difference to the factor that moved it: fewer API calls, less context…
ai-usage-review
Review recorded AI coding-tool usage and recommend concrete optimizations. Reads real token, cost, session and harness-configuration data from the AI Insights MCP server, then reports ranked, evidence-backed fixes — trimming instruction files, raising the prompt-cache hit rate, right-sizing models, cutting MCP…
Bun Patterns
Use this skill when working in Bun-based projects (or Node projects running on Bun) and you want reliable runtime expectations, dependency management, and debugging workflows.
Node.js Debugger
Use this skill when debugging runtime failures in Node.js or Bun: stack traces, async errors, startup crashes, port conflicts, and memory leaks.
google-meet
Google Meet via gws: create spaces, fetch join links, list recordings.
people-crm
Turn LinkedIn connections (or any contact export) into a queryable personal CRM using the agent database.