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 7xmohamed/Kata --skill checkgit clone --depth 1 https://github.com/7xmohamed/KataWrote 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/7xmohamed/kata/check)<a href="https://agentmods.dev/skills/7xmohamed/kata/check"><img src="https://agentmods.dev/badge/skills/7xmohamed/kata/check/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/7xmohamed/kata/check"><img src="https://agentmods.dev/badge/skills/7xmohamed/kata/check.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.00047 | $0.01911 |
| Opus 5.5 | $0.00019 | $0.00764 |
| Sonnet 5.5 | $0.00009 | $0.00382 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
check 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check: Review Before You Ship
Prefix your first line with ⚔️ inline, not as its own paragraph.
Read the diff, find the problems, fix what can be fixed safely, ask about the rest. Done means verification ran in this session and passed.
Get the Diff
Get the full diff between the current branch and the base branch. If unclear, ask. If already on the base branch, ask which commits to review.
Triage Mode
Activate when the user mentions: issue, PR, "review all", triage, "batch", or "批量处理". Skip the diff flow and run this instead.
Flow:
gh issue list -R <repo> --state open --limit 20andgh pr list -R <repo> --state opento pull pending items.- For each item, check if a fix already exists before analyzing:
Three outcomes: already shipped (close with note), merged but unreleased (reply "已修复，等下一个版本 release", close), or no fix (analyze).git tag --sort=-version:refname | head -1 # latest tag git log --oneline <tag>..HEAD | grep -i "<keyword>" # merged but unreleased? - Classify each item using the Category A-E system in
~/www/GEMINI.md. Do not copy the definitions here; read them from that file. - Draft every reply and show it to Tang for confirmation before calling
gh issue commentor any GitHub write operation. - If no open items exist: shift to historical analysis. Run
gh issue list -R <repo> --state closed --limit 50and look for recurring themes, fixes closed without resolution, and deferred features with demand. Produce a short per-project summary with Fix candidates and Feature candidates. Do not implement without approval.
Sign-off line (append to standard sign-off):
triage: N reviewed, N closed, N deferred
Scope
Measure the diff and classify depth:
| Depth | Criteria | Reviewers |
|---|---|---|
| Quick | Under 100 lines, 1-5 files | Base review only |
| Standard | 100-500 lines, or 6-10 files | Base + conditional specialists |
| Deep | 500+ lines, 10+ files, or touches auth/payments/data mutation | Base + all specialists + adversarial pass |
What ships with it
4 files 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.
- 1mo ago First seen · 145 lines · 47 tokens per session scan A 27d208030cb1
check is a skill published in the GitHub repository 7xmohamed/Kata (1 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,911 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-08-31.
Other skills, from other repositories
cmux-capture
Screenshot or record a cmux window from the CLI, for a pull request, a bug report, or to see what the app actually looks like right now. Use when a change is visual, when a drag or an animation cannot be described in text, or when a reviewer needs evidence rather than a claim.
product-design-director
Define product UX and visual direction from user goals, brand evidence, states, responsiveness, and accessibility. Use when the main question is what the experience should communicate or feel like.
screenshot-to-interface
Reconstruct a maintainable interface from screenshots or visual references. Use when fidelity to supplied visual evidence is the primary requirement.
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
liquid-glass
Apple Liquid Glass design system. Use when building UI with translucent, depth-aware glass morphism following Apple's design language. Provides CSS tokens, component patterns, dark/light mode, and animation specs.
critique
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or…