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 hnikoloski/imlazy --skill imlazy-routergit clone --depth 1 https://github.com/hnikoloski/imlazyWrote 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/hnikoloski/imlazy/imlazy-router)<a href="https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-router"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-router/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/hnikoloski/imlazy/imlazy-router"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-router.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.00038 | $0.00750 |
| Opus 5 | $0.00019 | $0.00375 |
| Sonnet 5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
imlazy-router 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 12d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
imlazy-router
Output contract
Output tier=<quick|std|heavy|vault|learn> and the name of the next skill to invoke.
If genuinely ambiguous between two adjacent tiers, ask ONE clarifying multiple-choice question and stop. Never multi-turn.
If the message has no actionable verb (e.g., the user said "i am lazy" with no ask), output tier=none and respond conversationally without loading any skills.
Classification heuristics
| Signal | Tier |
|---|---|
| Single-line content fix (typo, spelling, value, version bump) | quick |
| Single-file edit ≤30 lines, no new dependency added | quick |
| Factual question, code explanation, lookup | quick |
| Run a command (test, build, format, lint) without modifying code | quick |
| Single rename or import cleanup, no behavior change | quick |
| 1-3 file feature or bugfix with clear requirements | standard |
| Refactor of a single function or component | standard |
| Schema or config migration involving 2-3 files | standard |
| Single-concern enhancement (caching, validation, error handling, tracing) | standard |
| "create vault", "save knowledge", "vault init", "vault search" | vault |
| New subsystem (auth, billing, replay, notifications, collaboration) | heavy |
| User explicitly says "design", "plan", "architecture", or "let's build" | heavy |
| Multi-component feature with unclear integration points | heavy |
| Cross-cutting migration (e.g., REST to GraphQL across the whole API) | heavy |
| Router misclassification feedback from Skill(imlazy-learn) | learn |
Disambiguation
When the signal is between Quick and Standard: ask "Will this need a new test, or is it a content/config edit only?"
When the signal is between Standard and Heavy: ask "Are the requirements clear, or do we need to design this together first?"
Wait for ONE answer. Default to the lighter tier if the answer is still ambiguous.
Adaptive lookup
Before classifying, read up to the last 20 lines of ~/.claude/imlazy/heuristics.log if it exists.
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.
- 12d ago First seen · 65 lines · 38 tokens per session scan A 6fcc6cc37673
imlazy-router is a skill published in the GitHub repository hnikoloski/imlazy (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 750 once invoked, about $0.0002 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-31.
Other skills, from other repositories
code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
architecture-design
Use only when creating new registrable ML components that require Factory or Registry patterns.
results-analysis
This skill should be used when the user asks to "analyze experimental results", "run strict statistical analysis", "compare model performance", "generate scientific figures", "check significance", "do ablation analysis", or mentions interpreting experiment data with rigorous statistics and visualization. It focuses on…
review-response
Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
verification-loop
This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.