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 skills add rse/ase --skill ase-repo-reviewgit clone --depth 1 https://github.com/rse/aseWrote 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/rse/ase/ase-repo-review)<a href="https://agentmods.dev/skills/rse/ase/ase-repo-review"><img src="https://agentmods.dev/badge/skills/rse/ase/ase-repo-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.
<a href="https://agentmods.dev/skills/rse/ase/ase-repo-review"><img src="https://agentmods.dev/badge/skills/rse/ase/ase-repo-review.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.00109 | $0.04025 |
| Opus 5.5 | $0.00044 | $0.01610 |
| Sonnet 5.5 | $0.00022 | $0.00805 |
| Haiku 4.5 | $0.00011 | $0.00402 |
Grade A, and why
ase-repo-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 today.
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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
$ARGUMENTS
Procedure
-
-
-
Run the command
git rev-parse --verify --quiet "<getopt-option-branch/>^{commit}". If it fails, only output the following and then STOP immediately: -
Determine the candidate base branches by running the command
git for-each-ref --format="%(refname:short)" refs/heads/(taken exactly as given), excluding itself. For each , run the commandgit rev-list --count "<candidate/>..<getopt-option-branch/>"to count the commits of the branch since its fork point from , and drop every candidate with a count of0, as it already contains the branch. Set to the remaining candidate with the smallest count (the nearest fork point); on a tie, prefer the checked-out branch (the output ofgit branch --show-current), and then the first candidate. If no candidate remains, only output the following and then STOP immediately: -
Run the command
git merge-base "<base/>" "<getopt-option-branch/>"and capture its output into . -
Only output the following :
-
-
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +162 lines · +44 tokens per session af9beccce454
- 7d ago First seen · 211 lines · 65 tokens per session scan A cdc7c9d73eb4
ase-repo-review is a skill published in the GitHub repository rse/ase (57 stars, last pushed yesterday), licensed Apache-2.0. It adds 109 tokens to every session and 4,025 once invoked, about $0.0004 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-30.
Other skills, from other repositories
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
spec-finish
Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the user says "finish", "done", or "complete"…
git-commit-helper
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
github-refresh
Reviewed refresh and confirmed GitHub coordination write-back processor for tracker-origin artifacts.