review

review is a skill for Claude Code from odere-pro/claude-wiki-pages-plugin. It costs 82 tokens per session (1,743 once invoked), scanned A, original, MIT.

A human review workflow for checking drafted wiki pages before they become live pages. Drafts are kept in a proposed area that mirrors their eventual wiki location.

In plain words
What is it for?
Use it to inspect proposed pages, approve or reject them, promote approved drafts into the wiki, and run the follow-up maintenance process.
Why use it?
It prevents unreviewed content from entering the wiki and records who or what produced each draft before approval or rejection.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash scripts/check-duplicate-claims.sh \.

Part of the claude-wiki-pages plugin — 26 skills, 5 commands, 17 agents, 7 hooks shipped together

Good fit Use it to inspect proposed pages, approve or reject them, promote approved drafts into the wiki, and run the follow-up maintenance process.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/odere-pro/claude-wiki-pages-plugin
agentmods
npx agentmods add skills/odere-pro/claude-wiki-pages-plugin/review

Made for: Claude Code.

Or install claude-wiki-pages, the plugin that ships this one along with the rest of its 26 skills, 5 commands, 17 agents, 7 hooks.

Wrote 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.

agentmods badge for review

README.md
[![agentmods](https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/review/github.svg)](https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/review)
Your own site
<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/review"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/review/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.

agentmods 80×15 button for review

Your own site · 80×15
<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/review"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,743 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.01743
Opus 5 $0.00041 $0.00872
Sonnet 5 $0.00016 $0.00349
Haiku 4.5 $0.00008 $0.00174

Measured 10d ago against content hash 229aa3954ee1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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.

skills/review/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LLM Wiki — Review

The human-in-the-loop gate. Drafts (from a local model, or any source) land in vault/_proposed/, mirroring their eventual wiki/ path. Nothing reaches the wiki until a human approves it here.

The _proposed/ + proposed_by contract

This contract is the single review channel for all drafted content (src/commands/propose/propose.ts). There is exactly one _proposed/ channel — no second draft mechanism exists.

Directory layout

Drafts live at vault/_proposed/wiki/<topic>/<page>.md, mirroring the target path they would occupy in vault/wiki/<topic>/<page>.md. _proposed/ is a sibling of wiki/ inside the vault root.

vault/
├── wiki/                  # live wiki pages
│   └── <topic>/<page>.md
└── _proposed/             # staging area — outside all wiki-scoped checks
    └── wiki/
        └── <topic>/<page>.md  # mirrors the target wiki/ path

Frontmatter on a draft

Every draft carries:

  • status: draft — marks the page as not yet in the wiki.
  • proposed_by: "<source>" — records what produced the draft (e.g. "ollama:llama3", "claude", "local-ingest-stub"). Dropped on promotion — the promoted page carries no proposed_by field.

Outside every wiki-scoped check

Because _proposed/ is a sibling of wiki/, every wiki-scoped hook and gate (validate-frontmatter.sh, check-wikilinks.sh, lint, verify-ingest.sh, the source-index) treats drafts as out-of-scope until promotion. Drafts cannot pollute the wiki.

Promotion (approve)

propose approve is the only sanctioned promotion path. Do not hand-copy draft content into wiki/ — that bypasses the checkpoint and the frontmatter rewrite. On approval, the engine:

  1. Moves the file from _proposed/wiki/… to wiki/….
  2. Sets status: active.
  3. Drops proposed_by.
  4. Stamps updated with today's date.
  5. Commits the change as a git checkpoint → fully reversible via git revert <sha>.

Rejection

propose reject deletes the draft under a git checkpoint. Reversible via git revert <sha>.

Read the full file on GitHub · 179 lines

Changes

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.

  1. 10d ago First seen · 179 lines · 82 tokens per session scan A 229aa3954ee1

Subscribe to this mod's changes

review is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 1,743 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.

Related

Other skills, from other repositories

schema-evolve

This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…

voxpelli/vp-claude · 139 tokens

knowledge-maintain

This skill should be used when the user asks to fix, repair, or tidy one or more SPECIFIC named notes — 'fix these notes', 'fix the issues in [note]', 'add the missing relations to [note]', 'tidy up [note]', 'fix orphan [note]', 'apply the gardener findings for [note]'. Applies structural fixes (missing sections…

voxpelli/vp-claude · 183 tokens

raindrop-triage

This skill should be used when the user asks to 'triage unsorted bookmarks', 'clean up raindrop inbox', 'sort unsorted', 'organize bookmarks', 'raindrop triage', 'process bookmark backlog', 'promote triaged bookmarks', 'classify triaged', 'raindrop cleanup', 'deduplicate bookmarks', 'find duplicate bookmarks', 'tag…

voxpelli/vp-claude · 181 tokens

knowledge-garden

This skill should be used when the user asks to audit, health-check, or structurally validate one or more SPECIFIC named notes or a bounded topic cluster — 'audit these notes', 'check this note for orphans or broken links', 'fourth-wall check on [note]', 'validate the structure of [note]', 'spot-check [note]'. Runs a…

voxpelli/vp-claude · 152 tokens

nudge

This skill (explicit /nudge only) manages Claude Code feature-adoption nudges sourced from the Basic Memory note main/reference/claude-code-noteworthy-features. Bare /nudge = Mode A (sync): re-read the note, filter out features already marked adopted or declined, and regenerate the tip cache…

voxpelli/vp-claude · 210 tokens

session-bookmarks

This skill should be used to save URLs or links found this session as Raindrop bookmarks — triggers: 'bookmark URLs from this session', 'save links we found', 'save notable URLs to Raindrop', 'save session URLs', 'raindrop bookmarks from session'. Scans the current conversation for high-signal URLs discovered during…

voxpelli/vp-claude · 129 tokens