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 sentimony/skills --skill scope-checkgit clone --depth 1 https://github.com/sentimony/skillsWrote 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/sentimony/skills/scope-check)<a href="https://agentmods.dev/skills/sentimony/skills/scope-check"><img src="https://agentmods.dev/badge/skills/sentimony/skills/scope-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/sentimony/skills/scope-check"><img src="https://agentmods.dev/badge/skills/sentimony/skills/scope-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.00075 | $0.00895 |
| Opus 5.5 | $0.00030 | $0.00358 |
| Sonnet 5.5 | $0.00015 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
scope-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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Check
Give the user a readable HTML view of a saved spec or plan, and keep the folder index current. The Markdown file stays the source of truth; the HTML is a disposable view regenerated from it.
When It Runs
scope-triagecalls it after the spec self-review and again after every spec edit during the user's review.plan-craftingcalls it after saving the plan and again after review corrections, before the execution choice.- The user calls it as
/scope-check <path>on any saved spec or plan.
Run it on every save or edit of that file in the session, so the preview never shows a stale version.
Steps
-
Preview opt-out. The preview is off when the user said so in this conversation ("no HTML", "skip the preview") or the project's
AGENTS.mdorCLAUDE.mdsays so. No environment variable or argument controls it. When it is off, skip step 2 and the link in step 4, and still do step 3. -
Render. Run the bundled script from this installed skill directory with the absolute path of the Markdown file:
python3 <skill-dir>/scripts/render.py <absolute-path-to-file.md>It writes
<temp-dir>/scope-check/<repo>/<folder>/<file>.html, overwriting the previous render of the same file, and prints itsfile://URL. Nothing is written to the repository. -
README index. Only when the Markdown file's folder has a
README.mdthat holds a list of links to files in that folder:- add a line for the file in the format of the existing lines (date, title, link);
- place it where the list's order puts it - at the top of a newest-first list;
- take the title from the file's first
#heading; when a line for the file exists and the heading changed, update that line instead of adding another; - add no status. With no README, or a README without such a list, create nothing and add nothing.
-
Report. One line with the
file://URL so the user can click it. Do not open a browser.
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.
- today Changed · +69 lines · +48 tokens per session f10d2896f6ec
- 2d ago Changed · +3 lines 989909b376a1
- 5d ago Changed · -6 lines 0298a6bcf4c2
- 12d ago First seen · 13 lines · 27 tokens per session scan A 3dfc97837fda
scope-check is a skill published in the GitHub repository sentimony/skills (6 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 895 once invoked, about $0.0003 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-01.
Other skills, from other repositories
refactor
Expert code refactoring based on Martin Fowler's catalog — improve maintainability without changing behavior. Covers code smells, composing methods, moving features, organizing data, simplifying conditionals, method calls, and generalization. Triggers on: refactor, 重构, clean up, improve code, code smell, extract…
loop-it
An automated workflow that repeatedly fetches open GitHub issues, orders them by dependencies, implements them, reviews the changes, and ships them.
walkthrough
Generate a Phase-2 Walkthrough artifact (walkthrough.md) once implementation and verification are complete. Captures a Change Summary, Verification Steps (commands + unit tests + automated browser testing outcomes), Visual Proof (screenshots/recordings embedded directly in the file), and a Review Gate (final diff + PR…
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.
listenhub-tts
A text-to-speech tool that uses the ListenHub service to turn written text into audio, including short recordings, multi-speaker scripts, and long-form streamed speech.
understand
Review and understand freshly AI-generated code. Scans the current repo's uncommitted/branch changes and builds a Claude-style light-themed two-column webpage — left is the project folder tree of changed files, right is the selected file's syntax-highlighted diff (additions/deletions clearly distinguished from…