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 selvatuple/revibe-mcp --skill openclawgit clone --depth 1 https://github.com/selvatuple/revibe-mcpWrote 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/selvatuple/revibe-mcp/openclaw)<a href="https://agentmods.dev/skills/selvatuple/revibe-mcp/openclaw"><img src="https://agentmods.dev/badge/skills/selvatuple/revibe-mcp/openclaw/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/selvatuple/revibe-mcp/openclaw"><img src="https://agentmods.dev/badge/skills/selvatuple/revibe-mcp/openclaw.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.00025 | $0.02322 |
| Opus 5.5 | $0.00010 | $0.00929 |
| Sonnet 5.5 | $0.00005 | $0.00464 |
| Haiku 4.5 | $0.00003 | $0.00232 |
Grade A, and why
revibe scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- curl How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Analyze codebases to understand architecture, file roles, design patterns, execution flows, and system design decisions. Returns structured insights inline and saves agent_context.json for persistent codebase understanding.
Revibe turns any GitHub repository into a complete architecture map — modules, dependencies, call chains, design decisions — in about 2 minutes.
When to Use
- User asks to "analyze", "understand", or "explain" a codebase or repository
- User clones or forks a new repo and wants to understand it quickly
- User says "what does this project do" or "how is this structured"
- User asks about architecture, patterns, or design decisions of a repo
- Another skill needs codebase context to work effectively (use agent mode)
Behavior
Step 1: Extract the Target
Determine the GitHub URL from one of these sources (in priority order):
- Explicit URL in the message — e.g.,
https://github.com/owner/repoorowner/repo - Current working directory — If the user says "analyze this", "understand this project", or doesn't specify a repo, detect it automatically:
Convert SSH URLs to HTTPS:# Get GitHub URL from current git repo REMOTE_URL=$(git remote get-url origin 2>/dev/null)# [email protected]:owner/repo.git → https://github.com/owner/repo if [[ "$REMOTE_URL" == [email protected]:* ]]; then REMOTE_URL="https://github.com/${REMOTE_URL#[email protected]:}" fi # Strip .git suffix REMOTE_URL="${REMOTE_URL%.git}" - Ask the user — Only if not in a git repo and no URL provided: "Which repository would you like me to analyze?"
When using the current directory, confirm briefly: "Analyzing {repo_name} from your current directory..."
Step 2: Submit for Analysis
# Set up auth
API_KEY="${REVIBE_API_KEY:-}"
AUTH_HEADER=""
if [ -n "$API_KEY" ]; then
AUTH_HEADER="-H \"X-Revibe-Key: $API_KEY\""
fi
# Submit
RESPONSE=$(curl -s -X POST "https://app-backend.revibe.codes/api/v1/analyze" \
-H "Content-Type: application/json" \
${AUTH_HEADER} \
-d "{\"github_url\": \"${REMOTE_URL}\"}")
JOB_ID=$(echo "$RESPONSE" | jq -r '.job_id')
STATUS=$(echo "$RESPONSE" | jq -r '.status')
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 · 254 lines · 25 tokens per session scan A ae8888aae6c3
revibe is a skill published in the GitHub repository selvatuple/revibe-mcp (1 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 2,322 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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-diagram
Analyzes source code and generates Mermaid diagrams. Accepts a directory, file, @reference, line range (path:10-50), multiple targets ([path1, path2]), or pasted code. Supports class, sequence, component, and architecture diagrams for Dart, TypeScript, Python, Java, Kotlin, Go, Swift, Rust.
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
ix
Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
chisle-audit
One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer nor a pure prose compressor does both in…