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 agentmods add skills/clivejefferies/mobile-debug-tools/spec-reviewnpx skills add clivejefferies/mobile-debug-tools --skill spec-reviewgit clone --depth 1 https://github.com/clivejefferies/mobile-debug-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/clivejefferies/mobile-debug-tools/spec-review)<a href="https://agentmods.dev/skills/clivejefferies/mobile-debug-tools/spec-review"><img src="https://agentmods.dev/badge/skills/clivejefferies/mobile-debug-tools/spec-review.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00536 |
| Opus 5 | $0.00000 | $0.00268 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
spec-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 3d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Review skill
name: spec-review version: 0.1.1 summary: Reusable workflow for reviewing specs in this repository with a consistent readiness rubric and output template.
Purpose
Help an agent review a specification for clarity, implementation readiness, and execution readiness against the current codebase. Use a common template so reviews stay consistent across documents and reviewers.
Activation conditions
Activate when an agent needs to:
- review a new or revised spec
- assess whether a spec is implementation-ready or execution-ready
- identify whether feedback is a spec issue or an implementation issue
- compare a spec against the current
src/contract surface and docs
Surface area (actions)
- locate-spec
- compare-against-code
- assess-contract-completeness
- classify-gaps
- produce-review
Core guidance
- Read the spec first, then compare it against the relevant code, docs, and tests.
- Separate spec gaps from implementation gaps.
- Check for: problem clarity, scope boundaries, explicit contracts, acceptance criteria, non-goals, and consistency with existing behavior.
- Prefer precise feedback that names the missing contract, unclear rule, or inconsistent behavior.
- Use the shared review template in
references/spec-review-template.mdfor the final output. - If the spec is not ready, say exactly what must be clarified before implementation can start.
- Classify each blocker as either a spec gap or an implementation contract gap and stop at that boundary.
Inputs & outputs
- review-spec(input: { specPath, relatedPaths?, focusAreas? }) -> { verdict, risks, specGaps, implementationGaps, recommendations }
- compare-against-code(input: { specPath, codePaths[] }) -> { matches, mismatches, notes }
- produce-review(input: { specPath, findings[] }) -> { summary, verdict, checklist, nextStep }
Failure handling
- If the spec file is missing, stop and report the missing path explicitly.
- If the spec is ambiguous, classify each concern as either "spec" or "implementation" instead of blending them.
- If the review cannot be grounded in the current repo, state that the spec is not reviewable yet.
What ships with it
2 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.
- 3d ago First seen · 53 lines · 0 tokens per session scan A 4f9e909c49bb
spec-review is a skill published in the GitHub repository clivejefferies/mobile-debug-tools (7 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 536 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…