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 husniadil/ekstend --skill code-reviewgit clone --depth 1 https://github.com/husniadil/ekstendWrote 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/husniadil/ekstend/code-review)<a href="https://agentmods.dev/skills/husniadil/ekstend/code-review"><img src="https://agentmods.dev/badge/skills/husniadil/ekstend/code-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/husniadil/ekstend/code-review"><img src="https://agentmods.dev/badge/skills/husniadil/ekstend/code-review.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.00039 | $0.07755 |
| Opus 5.5 | $0.00016 | $0.03102 |
| Sonnet 5.5 | $0.00008 | $0.01551 |
| Haiku 4.5 | $0.00004 | $0.00775 |
Grade A, and why
code-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 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 — 676 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review - Iterative Review
An iterative, human-in-loop code review skill that identifies gaps, presents them for user selection, and fixes them in cycles until clean.
Review Modes
Two modes. Pick based on user intent — detail for each mode is covered in Step 0 below.
- PR Review Mode (default): diff-based review against a base branch
- Holistic Review Mode: audit an entire codebase or scoped directories
Subagent Mode (argument)
The skill accepts one optional argument via $ARGUMENTS controlling whether scans/fixes delegate to Task subagents:
$ARGUMENTS value |
Meaning |
|---|---|
subagent |
Always delegate eligible work to subagents — Explore for read-only scans (Step 0 Holistic, Step 5 re-review), general-purpose for multi-file complex fixes (Step 4) |
no-subagent |
Never call the Task tool. Do everything in the main context: Glob + Read + Grep directly, apply fixes directly |
auto |
Let the skill decide based on scope size, codebase breadth, and fix complexity |
| (empty) | Same as auto |
Default: auto. If $ARGUMENTS is empty or not recognized, operate in auto mode.
auto decision heuristics:
- Holistic scan over >50 files or multiple ecosystem packages → delegate to Explore subagent
- Fix touches >2 files or needs cross-cutting refactor → delegate to general-purpose subagent
- Small PR diff / single-file scope / known surface → stay in main context
- Tight budget / urgency signal from user → stay in main context
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 · 676 lines · 39 tokens per session scan A 130dfcb897dc
code-review is a skill published in the GitHub repository husniadil/ekstend (1 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 7,755 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
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-review
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.
coding-principles
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
vertical-onboarding
Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value…
spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIALID and data path.