ase-meta-review

ase-meta-review is a skill for Claude Code from rse/ase. It costs 64 tokens per session (2,076 once invoked), scanned A, original, Apache-2.0.

A review command that examines staged Git changes and returns a human-style approve-or-reject verdict with prioritized findings and line references.

In plain words
What is it for?
Use it to review staged files, identify issues by severity, and decide whether the changes should be approved.
Why use it?
It provides a structured check of changes before they are committed, while following special handling for projects whose source is treated as a black box.

Skill for Claude Code

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

Part of the ase plugin — 53 skills, 10 agents, 5 hooks shipped together

Good fit Use it to review staged files, identify issues by severity, and decide whether the changes should be approved.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rse/ase/ase-meta-review
Install

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.

Any agent
npx skills add rse/ase --skill ase-meta-review
Clone the repo
git clone --depth 1 https://github.com/rse/ase

Made for: Claude Code.

Or install ase, the plugin that ships this one along with the rest of its 53 skills, 10 agents, 5 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 ase-meta-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/rse/ase/ase-meta-review/github.svg)](https://agentmods.dev/skills/rse/ase/ase-meta-review)
Your own site
<a href="https://agentmods.dev/skills/rse/ase/ase-meta-review"><img src="https://agentmods.dev/badge/skills/rse/ase/ase-meta-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 ase-meta-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/rse/ase/ase-meta-review"><img src="https://agentmods.dev/badge/skills/rse/ase/ase-meta-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,076 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00064 $0.02076
Opus 5 $0.00032 $0.01038
Sonnet 5 $0.00013 $0.00415
Haiku 4.5 $0.00006 $0.00208

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

Security

Grade A, and why

ase-meta-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.

plugin/skills/ase-meta-review/SKILL.md · 211 lines

How it starts

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

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

$ARGUMENTS

Procedure

    1. Determine whether there are staged changes at all by running the corresponding command (taken exactly as given) and capturing its output - the bare list of staged file names - into . This is a lightweight gate; the full diff is fetched by the sub-agent in STEP 2, so capturing only the file-name list here is sufficient:

      git diff --cached --name-only HEAD

  1. The project source artifacts are classified as a black box, so the user does not want the staged changes scrutinized or their findings surfaced. Skip the entire review investigation: do not invoke the Agent tool and do not read any change, set to the empty list, set to SKIPPED (boxing: black), set to a one-line neutral restatement of the change intent derived solely from STEP 1, and proceed directly to STEP 3.

    First, use the following to give a hint on this step:

    Dispatch the review investigation to a sub-agent via the Agent tool so that no investigation details leak into the user-visible transcript. The sub-agent performs the silent reading, the read-only repository probing, and the critique; only its final structured return value is consumed here.

    For this, invoke exactly once the tool:

        Agent(
            description:       "Review Investigation",
            subagent_type:     "ase:ase-meta-review",
            prompt:            "Review the staged changes.",
            run_in_background: false
        )
    

    Parse the single result message of the Agent tool as a JSON object, set to its summary field (a single crisp sentence reconstructing the change's intent), and set to its findings field (a list).

    Then derive the overall from : set to REJECT - DEMANDS CHANGES if any finding in has a severity field of HIGH; otherwise set to APPROVE. The verdict is derived before the severity floor below, so the floor only affects which findings are rendered, never the verdict.

    Then determine the effective severity floor : define the ordinal rank LOW=1, MEDIUM=2, HIGH=3, start from (default LOW), and - if is equal grey - raise to MEDIUM whenever its current rank is below rank(MEDIUM) (grey boxing surfaces only material findings of severity MEDIUM and above). The floor affects only which findings are rendered, never the derived above.

Read the full file on GitHub · 211 lines

Files

What ships with it

1 file 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.

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 · 211 lines · 64 tokens per session scan A 74fe83ddfea1

Subscribe to this mod's changes

ase-meta-review is a skill published in the GitHub repository rse/ase (48 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 2,076 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

thedotmack/claude-mem · 44 tokens

github-review-pr

Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…

feiskyer/claude-code-settings · 90 tokens

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

a5c-ai/babysitter · 23 tokens

babysit

Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

michael-denyer/pstack-claude · 61 tokens

review-open-pull-requests

List and analyze all open pull requests across GitHub repositories. Shows review status, CI/CD check results, age, and reviewers. Use when triaging PRs, checking team velocity, or identifying stale reviews that need attention.

caipe-io/ai-platform-engineering · 52 tokens

review-pr

Perform a comprehensive code review of a pull request.

FlorianBruniaux/claude-code-ultimate-guide · 12 tokens