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/fo0/clawstash/reviewnpx skills add fo0/clawstash --skill reviewgit clone --depth 1 https://github.com/fo0/clawstashWrote 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/fo0/clawstash/review)<a href="https://agentmods.dev/skills/fo0/clawstash/review"><img src="https://agentmods.dev/badge/skills/fo0/clawstash/review.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.00081 | $0.00657 |
| Opus 5 | $0.00041 | $0.00329 |
| Sonnet 5 | $0.00016 | $0.00131 |
| Haiku 4.5 | $0.00008 | $0.00066 |
Grade A, and why
review 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review — Diff / Recent-Changes Code Review
When to Use
- User says "/review", "review this", "review the diff", "review my changes", "do a review"
- After implementing a feature — done-skill does NOT run review automatically (it stays predictable). User invokes review skill explicitly when they want it.
Source of Truth
The full review workflow lives in agent_docs/review_process.md. Do not duplicate it here. This skill is a thin invocation wrapper:
- Read
agent_docs/review_process.mdto load the current rules (severity definitions, categories, fixing rules, commit gate). - Determine review scope: diff vs full-read vs large-scale (>30 changed files).
- Execute the workflow as defined in the process file.
- Produce the standard
### Code Review Resultstable. - Write deferred findings to
BACKLOG.mdperagent_docs/backlog_process.md.
Workflow
1. git status + git diff -> identify changed files
2. Read agent_docs/review_process.md -> load rules
3. Run automated checks (lint / typecheck / test / build) per CLAUDE.md
4. (If GitNexus available) gitnexus_impact on changed symbols
5. Re-read every changed file completely
6. Evaluate against P0/P1/P2 categories
7. Fix P0/P1 inline; defer P2 only if non-trivial
8. Regression & complexity QA pass
9. UI review (only if UI changed)
10. Output standard Code Review Results table
11. Write deferred findings to BACKLOG.md
Rules
- Do not run automatically. This skill is on-demand only. Done-skill must NOT trigger it.
- No security-deep-dive here — for OWASP / injection / secrets / auth focus, use the separate
security-reviewskill. Generic review still covers Security at the P0 level perreview_process.md, butsecurity-reviewgoes deeper. - Output format is fixed — must produce the table defined in
review_process.mdso consumers (CI dashboards, follow-up prompts) can parse it. - Re-read files, never review from memory.
Report
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 · 66 lines · 81 tokens per session scan A 0be1f293a436
review is a skill published in the GitHub repository fo0/clawstash (1 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 657 once invoked, about $0.0004 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
@elad12390/web-research-assistant
Comprehensive MCP server for web research with 14 tools: SearXNG + Exa AI search, URL crawling, stealth scraping (Cloudflare bypass), package registry lookup (npm/PyPI/crates), GitHub stats, changelog fetching, tech comparison, error translation, API docs discovery, stock image search, and service health. Trigger…
business-model-validator
Use when a prospect, new customer, or existing operator wants to know whether Zooza fits their business, or which Zooza features map to how they operate. No Zooza account required — works as a pure knowledge interview.
spotify-mcp-doctor
Diagnose and repair NovaLux12/spotify-mcp-server failures — auth, permissions, devices, rate limits, OpenClaw wiring. Use when Spotify tool calls fail or setup stalls.
delegacion-local
Regla y catálogo para delegar pasos mecánicos (resumir, clasificar, extraer, boilerplate, mensaje de commit desde un diff, traducir texto o archivo, resumir salida de lint/tests/CI, explicar código, describir una imagen, verificar si el backend local está disponible) a modelos locales vía las tools local del MCP…
class-management
Use when the user wants to create a new class, group, or course in Zooza — e.g. "set up a Monday yoga class", "add a new group", "schedule a course". Guides through programme selection, venue, trainer, session pattern, and commits.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).