Borrowing it
Nothing to install: this file belongs to xsovad06/sova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.agents/skills/sova-review-full/SKILL.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/sova-review-full)<a href="https://agentmods.dev/skills/xsovad06/sova/sova-review-full"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-review-full/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.
<a href="https://agentmods.dev/skills/xsovad06/sova/sova-review-full"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-review-full.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00976 |
| Opus 5.5 | $0.00014 | $0.00390 |
| Sonnet 5.5 | $0.00007 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
sova-review-full 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Review Pipeline
Run a complete pre-push quality pipeline: simplify code, review for issues, then organize commits into clean history.
Scope: the arguments provided when this skill is invoked
Phase 1: Simplify
Follow the sova-simplify skill workflow. Review all changed code for opportunities to reduce complexity:
-
Get the diff scope:
BASE=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's#^origin/##') BASE=${BASE:-main} git fetch --quiet origin "$BASE" git diff "origin/$BASE"...HEAD --stat git diff --cached --stat git diff --stat -
For each changed file, read the entire file and check:
- Code reuse: does new code duplicate existing utilities or helpers? Search the codebase.
- Over-engineering: unnecessary abstractions, premature generalization, excessive configurability
- Dead code: unused imports, unreachable branches, commented-out code
- Redundancy: repeated logic that could be a shared helper (only if 3+ occurrences)
- Complexity: can any function be simplified without losing clarity?
- Efficiency: redundant computations, repeated file reads, duplicate API calls
-
Apply simplifications directly. After each change, verify tests still pass (see CLAUDE.md for commands).
-
If no simplifications are needed, state that and move on.
Phase 2: Review
Follow the sova-review skill workflow:
- Review all changed files for bugs, security, performance, test coverage, consistency, doc freshness, and scout rule (fix pre-existing issues in touched files).
- Score each finding (1-10 priority). Address all findings (fix or acknowledge with justification).
- Run the full CI-equivalent checks:
make check. Fix any failures before proceeding. - Report findings in the standard review format.
See the sova-review skill for the full review checklist and scoring criteria.
Phase 3: Organize Commits
Follow the sova-rearrange-commits skill workflow:
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.
- 14d ago Changed · +3 lines 7c24baef7efa
- 16d ago Changed · +1 tokens per session ead276673294
- 22d ago First seen · 89 lines · 33 tokens per session scan A e3da94c91bff
sova-review-full is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 976 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-10-08.
Other skills, from other repositories
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
loop-gh-pr
A recipe for a scheduled GitHub pull-request watcher. It checks open pull requests for new activity and prepares read-only review drafts without posting comments or merging anything.
git-iris
Use this skill when generating commit messages, pull request descriptions, release notes, changelogs, or code reviews in a repository where git-iris is available. Activates on requests like "commit this", "write a commit message", "draft a PR", "generate release notes", "write a changelog", or "review my changes" when…
requesting-code-review
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
fix
Read this repo's open issues, triage them, and open one pull request per issue that can be fixed without a judgement call. Issues that need a decision, or that look stale or superseded, are reported with a recommendation rather than guessed at.
git
This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", or performs any git/GitHub operation.