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-planninggit 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-planning)<a href="https://agentmods.dev/skills/hnikoloski/imlazy/imlazy-planning"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-planning/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-planning"><img src="https://agentmods.dev/badge/skills/hnikoloski/imlazy/imlazy-planning.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.00044 | $0.01613 |
| Opus 5 | $0.00022 | $0.00807 |
| Sonnet 5 | $0.00009 | $0.00323 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
imlazy-planning 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 11d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
imlazy-planning
Mode selection
Light mode — used when the router classified Standard tier. Output: 3-7 bullet inline plan in the chat. No plan doc saved. Execute inline in the same session.
Full mode — used when the router classified Heavy tier and brainstorming has already produced a spec doc. Output: a saved plan doc at docs/imlazy/plans/YYYY-MM-DD-<feature>.md. Execution dispatches a fresh subagent per task with two-stage review (spec-compliance then code-quality).
The router-selected mode is fixed for this task — do not switch modes mid-execution.
Light mode: plan structure (Standard tier)
Write a 3-7 bullet plan inline:
Plan (light mode):
1. <one-sentence action — file — expected change>
2. Write failing test for <behavior>
3. Implement <function> in <file> to pass the test
4. Verify: run <test command>, confirm pass
5. Commit: git commit -m "feat: <description>"
Rules: each bullet names a file and what changes. TDD bullets are always inline (test → implement → verify). No TBD placeholders.
Full mode: plan document (Heavy tier)
File structure first
Before defining tasks, map which files are created or modified and what each one is responsible for. Each file has one clear responsibility. Files that change together live together. Split by responsibility, not by technical layer.
Bite-sized task granularity
Each step is one action (2-5 minutes):
- "Write the failing test" — step
- "Run it to make sure it fails" — step
- "Implement the minimal code to make it pass" — step
- "Run the tests and make sure they pass" — step
- "Commit" — step
Plan document header
Every plan doc must start with:
# [Feature Name] Implementation Plan
> For agentic workers: use `Skill(imlazy-planning)` in full mode to execute this plan task-by-task.
> Steps use checkbox (`- [ ]`) syntax for tracking.
**Goal:** [One sentence]
**Architecture:** [2-3 sentences]
**Tech Stack:** [Key technologies]
---
Task structure
What ships with it
3 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.
- 11d ago First seen · 175 lines · 44 tokens per session scan A ac483f68b01b
imlazy-planning is a skill published in the GitHub repository hnikoloski/imlazy (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,613 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.
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…
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.