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-bootstrapgit 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-bootstrap)<a href="https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-bootstrap"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-bootstrap/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-bootstrap"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-bootstrap.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.00032 | $0.00492 |
| Opus 5 | $0.00016 | $0.00246 |
| Sonnet 5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
imlazy-bootstrap 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
imlazy-bootstrap
Triggers
When the user message starts with /imlazy <task> or i am lazy, <task> (at the start of a message or as a clear prefix), invoke Skill(imlazy-router) with the task description.
Additionally, detect VAULT triggers: "vault init", "vault save", "vault search", "create vault" — route these to Skill(imlazy-router) for vault-tier classification.
Do NOT trigger on "i am lazy" appearing mid-paragraph or without an actionable verb (e.g., "i am lazy and tired today" is not a trigger — no action to route).
The slash command /imlazy is a hard trigger. The chat phrase requires a clear actionable ask.
The 1% rule
If a skill might apply to what you are doing, invoke it before responding. After triggering, the router decides which workflow skills to load — you do not need to pre-load anything yourself.
Instruction priority
User instructions in CLAUDE.md / AGENTS.md take precedence over imlazy skills, which take precedence over default system behavior. The router never overrides explicit user requests — if the user says "skip the plan", honor it.
Quick-tier completion gate
For Quick-tier tasks (classified as such by imlazy-router), before claiming completion:
- Run the relevant verification command — test suite, build, or
git difffor content-only edits. - Confirm exit code 0 and the intended change is present in the output.
- If verification passes: claim completion, you are done.
- If verification fails: do NOT claim completion. Escalate to Standard tier:
- Invoke
Skill(imlazy-tdd)andSkill(imlazy-planning)(light mode). - Invoke
Skill(imlazy-learn)with predicted=quick, actual=standard, and a 50-char task summary. - Continue with the broader skill set loaded — do not restart the task from scratch.
- Invoke
What this skill does not do
This bootstrap deliberately omits red-flags tables, rationalization lists, and workflow philosophy — those live in the tier-specific skills, loaded lazily by the router.
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 · 41 lines · 32 tokens per session scan A 3d5edf9dd949
imlazy-bootstrap is a skill published in the GitHub repository hnikoloski/imlazy (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 492 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.