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 jmylchreest/aide --skill reviewgit clone --depth 1 https://github.com/jmylchreest/aideWrote 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/jmylchreest/aide/review)<a href="https://agentmods.dev/skills/jmylchreest/aide/review"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/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/jmylchreest/aide/review"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 118 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 120 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 121 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 123 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 124 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00014 | $0.02928 |
| Opus 5 | $0.00007 | $0.01464 |
| Sonnet 5 | $0.00003 | $0.00586 |
| Haiku 4.5 | $0.00001 | $0.00293 |
Grade A, and why
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 10d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Mode
Recommended model tier: smart (opus) - this skill requires complex reasoning
Comprehensive code review covering quality, security, and maintainability.
Review Checklist
Decision Conformance
Recorded decisions are this project's binding architectural commitments. Check them first — a conformance violation outranks any style or quality issue below.
- Called
decision_list(or noted the fallback) before reading any code - Every changed file checked against every decision that could apply to it
- Every ✅ backed by a cited check, not by inspection alone
- Every decision on its own line, including the ones that do not apply — no bulk dismissals
- "Decisions loaded: N" counted, not estimated, and matching the number of lines
- No decision violated by the change under review
- Change does not extend a pre-existing violation
- Where a decision seems wrong rather than the code, that is stated explicitly
Code Quality
- Clear naming (variables, functions, classes)
- Single responsibility (functions do one thing)
- DRY (no unnecessary duplication)
- Appropriate abstraction level
- Error handling coverage
- Edge cases considered
Security (OWASP Top 10)
- Input validation (no injection vulnerabilities)
- Authentication checks (routes protected)
- Authorization (proper access control)
- Sensitive data handling (no secrets in code)
- SQL/NoSQL injection prevention
- XSS prevention (output encoding)
- CSRF protection
- Secure dependencies (no known vulnerabilities)
Maintainability
- Code is readable without comments
- Comments explain "why" not "what"
- Consistent with codebase patterns
- Tests cover critical paths
- No dead code
Performance
- No N+1 queries
- Appropriate caching
- No memory leaks
- Efficient algorithms
Context-Efficient Reading
Prefer lightweight tools first, then read in detail where needed:
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.
- 10d ago First seen · 283 lines · 14 tokens per session scan A 92f0ad6fa408
review is a skill published in the GitHub repository jmylchreest/aide (17 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 2,928 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
simplify
Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with /simplify or /simplify .
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.