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.
npx agentmods add skills/scottarbeit/grace/code-review-stabilizernpx skills add ScottArbeit/Grace --skill code-review-stabilizergit clone --depth 1 https://github.com/ScottArbeit/GraceWrote 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.
[](https://agentmods.dev/skills/scottarbeit/grace/code-review-stabilizer)<a href="https://agentmods.dev/skills/scottarbeit/grace/code-review-stabilizer"><img src="https://agentmods.dev/badge/skills/scottarbeit/grace/code-review-stabilizer.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00040 | $0.00393 |
| Opus 5 | $0.00020 | $0.00197 |
| Sonnet 5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
code-review-stabilizer 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 4d 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.
What it actually says
Code review stabilizer
This skill is no longer an active Grace workflow authority.
Use the installed dev-process skill instead, especially:
dev-process/SKILL.md, sections on bounded R1 discovery review, R2 closure review, stop signals, and supersession;dev-process/CODE_REVIEW.mdfor Product V1 realistic-producer filtering and review modes;dev-process/TEMPLATES.mdfor the Review Discovery Ledger, Closure Review, Decision Packet, and Supersession Salvage Map;- repository
docs/Development process.mdfor Grace-specific branch, CI, PR, and cleanup mechanics.
Compatibility behavior
When an older prompt invokes this skill:
- Do not resume an unbounded review and repair loop.
- Load the current
dev-processauthority. - Reconstruct one finite R1 Review Discovery Ledger from supported current findings.
- Classify product decisions, new invariants, authority changes, and state-machine additions as owner stops.
- Route accepted in-scope findings to the existing issue-owner worker for one consolidated repair pass.
- Use one targeted R2 closure review.
- Do not start an automatic R3 whole-diff review. If closure incidentally exposes one supported-world merge blocker
outside the frozen ledger, record
DISCOVERY ESCAPEand stop rather than ignoring it or continuing discovery. - Simplify, split, or supersede when the finite closure protocol cannot converge.
Migration
Update prompts or documents that still route Grace review recovery here. New Grace work should reference dev-process
directly. Remove this compatibility skill after no active project source links to it.
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.
- 4d ago First seen · 38 lines · 40 tokens per session scan A 2f2f05044add
code-review-stabilizer is a skill published in the GitHub repository ScottArbeit/Grace (588 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 393 once invoked, about $0.0002 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.
Other skills, from other repositories
rust-code-quality
Run a focused Rust quality review when the user requests one, when reviewing a Rust PR/commit, or when another selected review workflow delegates Rust-specific checks. Do not auto-load for every implementation edit.
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
agent-session-monitor
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…