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-learngit 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-learn)<a href="https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-learn"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-learn/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-learn"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-learn.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.00378 |
| Opus 5 | $0.00019 | $0.00189 |
| Sonnet 5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
learn 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.
What it actually says
learn
When to invoke
- Auto-escalation fired: the router classified Quick, work started, verification failed, escalated to Standard. Log it.
- User feedback: user signals classification was wrong ("this didn't need all that ceremony" or "this was bigger than you thought"). Log it.
What to write
Append one line to ~/.claude/imlazy/heuristics.log (create the directory if needed):
<ISO-8601-timestamp>\t<predicted-tier>\t<actual-tier>\t<task-summary-50chars>
Example:
2026-05-15T14:32:00Z quick standard add a /health endpoint
Implementation
mkdir -p ~/.claude/imlazy
printf '%s\t%s\t%s\t%.50s\n' \
"$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
"$PREDICTED_TIER" \
"$ACTUAL_TIER" \
"$TASK_SUMMARY" \
>> ~/.claude/imlazy/heuristics.log
How the router uses it
lazy-router reads the last 20 lines of this file on every classification. Recent (≤30 days) misclassification patterns shift borderline classifications toward the tier that turned out correct in similar past cases.
What NOT to log
- Successful classifications — signal-to-noise only (log misclassifications only).
- Task content beyond 50 chars — truncation limits accidental leakage of sensitive task descriptions.
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 · 46 lines · 39 tokens per session scan A 5f5d0d5be4a2
learn is a skill published in the GitHub repository hnikoloski/imlazy (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 378 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.
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.
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.