What is review-criteria?

A review guide for classifying Datapages findings by where they affect users and how serious they are, then writing review reports. It is intended for code reviews and security audits.

Use it to classify findings as production, development, or repository issues and document their reach and severity in review files.

It prevents reviewers from confusing where a symptom appears with where its underlying cause runs. That distinction helps set the right priority and remediation scope.

How romshark/datapages configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to romshark/datapages. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/romshark/datapages/main/.claude/skills/review-criteria/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/romshark/datapages

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/romshark/datapages/review-criteria/github.svg)](https://agentmods.dev/skills/romshark/datapages/review-criteria)

Your own site

<a href="https://agentmods.dev/skills/romshark/datapages/review-criteria"><img src="https://agentmods.dev/badge/skills/romshark/datapages/review-criteria/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/romshark/datapages/review-criteria"><img src="https://agentmods.dev/badge/skills/romshark/datapages/review-criteria.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,157 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.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.01157
Opus 5.5	$0.00012	$0.00463
Sonnet 5.5	$0.00006	$0.00231
Haiku 4.5	$0.00003	$0.00116

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

Security

Grade A, and why

review-criteria 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 25d 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.

.claude/skills/review-criteria/SKILL.md · 90 lines

How it starts

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

Reach

Reach describes where the cause runs, not where the symptom appears.

Production: users' deployed servers and their visitors' browsers.
- The root package, runtime/, modules/, and modules/offline/sw.js.
- Generated datapagesgen, including committed example and acceptance output.
- Files datapages init writes from internal/generator/skeleton.
- .github/workflows/release.yml and .goreleaser.yaml.
Development: the developer's machine and CI.
- The CLI, parser, and generator, including crashes, wrong diagnostics, and generated code that does not compile.
- datapages watch and code gated by datapages.IsDevMode.
- Agent skills under internal/generator/agentdocs/data.
Repository: code no user application runs.
- Examples and acceptance cases outside datapagesgen, internal/tools/, magefiles/, docs/, and tests.

Apply these exceptions:

A defect found in an example has the reach of its cause. An example XSS caused by runtime/htmlattr has production reach.
A datapages.IsDevMode branch has development reach unless a request can enable it; then it has production reach.
An unsafe example pattern has repository reach. Recommend the documentation or skill that should warn against it.
Application responsibilities listed in SECURITY.md are not framework vulnerabilities. Missing guidance is Info.

Severity

Rate impact as if the cause ran in production:

Critical: a remote client needs only network access to run server code, run JavaScript in another visitor's browser, or read or change another session's data.
High: Critical impact behind an attacker-controlled precondition, such as an account or a documented application pattern; a few requests crash or hang the server; a correct application silently loses a write or misroutes data.
Medium: a common path fails with a workaround; sustained load grows memory or goroutines without bound; paths, versions, or timing leak without direct value to an attacker.
Low: unusual input or configuration causes a defect; a diagnostic or log is wrong; code is slow outside a hot path.
Info: no defect. Use for hardening, test gaps, and unclear documentation.

Read the full file on GitHub · 90 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.

25d ago Changed a83faf98b2a7
1mo ago First seen · 90 lines · 30 tokens per session scan A 9b1609d5d577

Subscribe to this mod's changes

review-criteria is a skill published in the GitHub repository romshark/datapages (119 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,157 once invoked, about $0.0001 per session on Opus 5.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-09-27.

Code review Frontend Go Security datastar framework nats templ

review-criteria next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
review-criteriaromshark/datapages	Skill	119	2d ago	MIT	A	30	Claude Code
printing-press-output-reviewmvanhorn/cli-printing-press	Skill	4.9k	yesterday	MIT	A	102	Claude Code
pr-to-go-lintergithub/gh-aw	Skill	5.6k	yesterday	MIT	A	22	Claude Code, Codex
reviewvercel/eve	Skill	5.8k	today	Apache-2.0	A	31	Claude Code, Codex
red-team-reviewwinstonkoh87/Athena-Public	Skill	620	yesterday	MIT	A	103	Claude Code
code-reviewjrswab/axe	Skill	909	15d ago	Apache-2.0	A	0	Claude Code, Codex
Smart Code ReviewAgentEra/Agently	Skill	1.7k	24d ago	Apache-2.0	A	47	Claude Code, Codex

datapages: Skill for Claude Code