review-feedback-schema

review-feedback-schema is a skill for Claude Code from existential-birds/beagle. It costs 27 tokens per session (2,356 once invoked), scanned A, original, Apache-2.0.

A structured record format for storing the results of code reviews, including the file, rule, issue, severity, decision, and reason. It is meant to show which review rules are useful or produce incorrect warnings.

In plain words
What is it for?
Use it when recording whether a review finding was accepted, rejected, deferred, or acknowledged, and when analysing review patterns.
Why use it?
It prevents review feedback from being kept as inconsistent notes and makes it possible to find false positives and measure review quality over time.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Part of the beagle-core plugin — 19 skills shipped together

Good fit Use it when recording whether a review finding was accepted, rejected, deferred…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/existential-birds/beagle/review-feedback-schema
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 existential-birds/beagle --skill review-feedback-schema
Clone the repo
git clone --depth 1 https://github.com/existential-birds/beagle

Made for: Claude Code.

Or install beagle-core, the plugin that ships this one along with the rest of its 19 skills.

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-feedback-schema

README.md
[![agentmods](https://agentmods.dev/badge/skills/existential-birds/beagle/review-feedback-schema.svg)](https://agentmods.dev/skills/existential-birds/beagle/review-feedback-schema)
Your own site
<a href="https://agentmods.dev/skills/existential-birds/beagle/review-feedback-schema"><img src="https://agentmods.dev/badge/skills/existential-birds/beagle/review-feedback-schema.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,356 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.00027 $0.02356
Opus 5 $0.00014 $0.01178
Sonnet 5 $0.00005 $0.00471
Haiku 4.5 $0.00003 $0.00236

Measured 7d ago against content hash 8a1118246212, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

review-feedback-schema 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 7d 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.

plugins/beagle-core/skills/review-feedback-schema/SKILL.md · 199 lines

How it starts

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

Review Feedback Schema

Purpose

Structured format for logging code review outcomes. This data enables:

  1. Identifying rules that produce false positives
  2. Tracking skill accuracy over time
  3. Automated skill improvement via pattern analysis

Schema

date,file,line,rule_source,category,severity,issue,verdict,rationale
Field Type Description Example Values
date ISO date When review occurred 2025-12-23
file path Relative file path amelia/agents/developer.py
line string Line number(s) 128, 190-191
rule_source string Skill and rule that triggered issue python-code-review/common-mistakes:unused-variables, pydantic-ai-common-pitfalls:tool-decorator
category enum Issue taxonomy type-safety, async, error-handling, style, patterns, testing, security
severity enum As flagged by reviewer critical, major, minor
issue string Brief description Return type list[Any] loses type safety
verdict enum Human decision ACCEPT, REJECT, DEFER, ACKNOWLEDGE
rationale string Why verdict was chosen pydantic-ai docs explicitly support this pattern

Gates (feedback log rows)

Run in order before appending a row. Do not skip ahead while a gate fails.

  1. Evidence bound to code

    • Pass when: file is a repo-relative path that exists (or existed at review time), and line identifies line number(s) you actually opened—not only a paraphrased summary.
  2. Rule source attributable

    • Pass when: rule_source matches skill-name[/section]:rule-id (see Rule Source Format). If the trigger is unknown, set a best-effort source and state the gap in rationale instead of inventing a rule id.
  3. Verdict backed by artifact

    • Pass when: For REJECT, rationale cites something checkable (command + output, doc URL, or quoted code). For ACCEPT, it states the fix or points to the change. For DEFER/ACKNOWLEDGE, it names a tracker, timeline, or documented intent per Verdict Types.

Read the full file on GitHub · 199 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. 7d ago First seen · 199 lines · 27 tokens per session scan A 8a1118246212

Subscribe to this mod's changes

review-feedback-schema is a skill published in the GitHub repository existential-birds/beagle (80 stars, last pushed 28d ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,356 once invoked, about $0.0001 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