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 signalcompose/claude-tools --skill checkupgit clone --depth 1 https://github.com/signalcompose/claude-toolsWrote 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/signalcompose/claude-tools/checkup)<a href="https://agentmods.dev/skills/signalcompose/claude-tools/checkup"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/checkup/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/signalcompose/claude-tools/checkup"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/checkup.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.00092 | $0.01038 |
| Opus 5.5 | $0.00037 | $0.00415 |
| Sonnet 5.5 | $0.00018 | $0.00208 |
| Haiku 4.5 | $0.00009 | $0.00104 |
Grade A, and why
checkup 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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/code:checkup — pre-merge reminder list
MANDATORY framing: This skill is a reminder, not a verifier. Its job is to surface items the user may want to consider before merging. It MUST NOT:
- Claim any item is "done" or "not done"
- Declare "all clear" or "ready to merge"
- Infer status from flags, logs, timestamps, or git history
The user reads the surfaced list, judges each item, and acts. Accuracy of judgement belongs to the user, not to this skill.
How to present the list
Output a single flat list. For each core item, one line of item name — purpose.
No check marks. No status columns. No categorization by "likely done" vs "likely
pending". Each item is presented as a prompt for the user to consider.
Core checklist (hardcoded, apply to every run)
Always surface all of these:
- simplify — has
/simplify(or equivalent) been run on this diff for reuse / quality / efficiency? - pr-review-team — has
/code:pr-review-teambeen run with explicit iterate-till-c=0-i=0 instruction? - secret scan — has
/code:trufflehog-scan(or equivalent) been run recently? - .gitignore security patterns — does
.gitignorehave thecode:security-patternsmarker? (Thecheck-gitignore-security.shpre-commit hook already guards this; surface here as reminder in case the hook is disabled.) - tests — do project tests pass locally against the current working tree?
- docs — if behavior or public API changed, is the documentation updated?
Project-specific checklist (read from CLAUDE.md)
Read the current project's CLAUDE.md (both ~/.claude/CLAUDE.md and the
project-local one if present). Scan for explicit pre-merge / pre-ship / pre-commit
items the project calls out. Surface anything you find as additional list entries
in the same flat format.
Do not invent items that aren't in CLAUDE.md. Do not summarize what the project does. Only surface explicit "remember to do X before merging / shipping / committing" items.
If CLAUDE.md mentions nothing pre-merge specific, that section is simply absent from the output.
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.
- 1mo ago First seen · 103 lines · 92 tokens per session scan A 270864b7a88d
checkup is a skill published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,038 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…