GocciaScript: Skill for Claude Code

.agents/skills/code-review/SKILL.md

code-review is a skill for Claude Code, Codex from frostney/GocciaScript. It costs 52 tokens per session (3,360 once invoked), scanned A, original, MIT.

A read-first review workflow for a pull request, branch, or worktree, where a worktree is a separate working copy of a repository. It produces evidence-backed findings and can recheck or fix findings only when explicitly authorized.

In plain words
What is it for?
Use it for fresh code reviews, targeted revalidation, or bounded remediation of selected review findings.
Why use it?
It separates judging a change from changing it, reducing accidental edits during review. It also keeps a whole-change review distinct from checking earlier findings again.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

This is frostney/GocciaScript's own configuration. It tells Claude Code and Codex how to work on GocciaScript itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything GocciaScript configures →

Reuse

Borrowing it

Nothing to install: this file belongs to frostney/GocciaScript. 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/frostney/GocciaScript/main/.agents/skills/code-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/frostney/GocciaScript

Made for: Claude Code, Codex.

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 code-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/frostney/gocciascript/code-review"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,360 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.00052 $0.03360
Opus 5.5 $0.00021 $0.01344
Sonnet 5.5 $0.00010 $0.00672
Haiku 4.5 $0.00005 $0.00336

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

Security

Grade A, and why

code-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 yesterday.

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.

.agents/skills/code-review/SKILL.md · 294 lines

How it starts

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

Code review

Establish whether the requested review scope is correct, necessary, clear, and ready for its claimed use. Without an explicit file or prior-findings input, review the complete change. Review first; remediate only in an authorized fix mode.

Operations, remediation, and boundaries

Choose one operation before gathering evidence:

  • Fresh review: judge the bounded change and issue a review verdict.
  • Targeted revalidation: recheck selected prior findings without judging the change as a whole.
  • Combined: perform both only when the user explicitly requests a fresh review and supplies prior findings; keep their outputs and conclusions separate.

Remediation is independent of the operation:

  • Default remediation is none. Inspect and run safe local probes, but do not edit source, tests, configuration, or documentation.
  • fix <finding IDs> fixes only the selected findings; fix-all fixes every validated in-scope finding in one bounded pass. With prior findings, either mode may edit only for selected findings classified still_present or changed, never for resolved, not_retestable, or skippedOutOfScope findings.
  • Fix modes authorize local edits and validation, not commits, pushes, PR comments, review-thread changes, deployments, publication, or shared-state mutation. Stop remediation for a material product, architecture, security, compatibility, or scope decision.
  • A request to save JSON authorizes only the named findings artifact; it does not authorize remediation.
  • Exact file lists and prior-findings JSON are additive inputs. They do not change unscoped review behavior unless the user supplies them.
  • A reporting profile or threshold changes presentation only. Gather and validate the complete candidate set across the mapped scope, retain every supported severity in the canonical result, and let the caller decide which severities become visible.
  • Search the complete mapped scope; do not stop after the first or highest-severity issue.
  • Delegate review lanes by default when the host supports subagents and the scope is not trivial. A small change, such as a few lines in one file, stays local. no-subagents or an equivalent user instruction keeps the whole review local. When the review delegates lanes, read references/subagent-lanes.md before publishing the lane map. While lanes run, the coordinator continues its own lane-independent work, such as running the project gate.

Read the full file on GitHub · 294 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. yesterday Changed · +10 lines ee3c8141c956
  2. 22d ago Changed · +10 lines 1f34f52c913b
  3. 26d ago Changed · -5 lines · +23 tokens per session 22a6a8cba311
  4. 29d ago First seen · 279 lines · 29 tokens per session scan A a490ff351652

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 3,360 once invoked, about $0.0002 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-26.

Related

Other skills, from other repositories

git-step-commit

Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…

bosens-China/tc39-atlas · 134 tokens

file-line-audit

Audit oversized source files in a repository. Apply repository .gitignore rules plus extra exclude patterns, filter candidate files with include glob patterns, count physical lines, and output only files at or above the threshold. Use this skill when the user asks to find long files, review file-length distribution…

bosens-China/tc39-atlas · 74 tokens

triage-contributor-pr

Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…

prisma/orm · 131 tokens

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

review-triage-phase

Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.

prisma/orm · 36 tokens

no-bare-casts

Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.

prisma/orm · 52 tokens