A completion-tracking system for substantial engineering work. It records observable success conditions, the checks that prove them, and the evidence collected from files or command results.

Use it for large tasks, exhaustive verification, completion ledgers, or work that needs durable evidence and runnable checks.

It makes “done” verifiable instead of relying on a list of attempted tasks. Unachievable checks can be recorded explicitly rather than quietly dropped.

unlazy — Skill for Claude Code and Codex by jkomyno

Install

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.

Any agent

npx skills add jkomyno/.dotfiles --skill unlazy

Clone the repo

git clone --depth 1 https://github.com/jkomyno/.dotfiles

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jkomyno/.dotfiles/unlazy/github.svg)](https://agentmods.dev/skills/jkomyno/.dotfiles/unlazy)

Your own site

<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/unlazy"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/unlazy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/unlazy"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/unlazy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 564 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.00564
Opus 5	$0.00015	$0.00282
Sonnet 5	$0.00006	$0.00113
Haiku 4.5	$0.00003	$0.00056

Measured 12d ago against content hash c4c34f4bf991, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

unlazy 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.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/gate-check.mjs, scripts/install-hooks.mjs, scripts/stop-hook.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

target/home/.agents/skills/unlazy/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Unlazy

Use durable evidence when ordinary planning and verification are not enough. The distinctive mechanism is a gate ledger; rely on the host's existing rules for scope, safety, planning, testing, and communication.

Start with gates

Before implementation, create GATES.md from templates/gates-leaf.md. Read references/gates.md before writing the first ledger.

State observable outcomes, not activities.
Give each automatable gate a CHECK, decisive EXPECT, and EVIDENCE.
Keep manual evidence short and concrete: a measurement, deciding output, or a file and line.
Preserve an impossible gate with ABANDON: <id> <reason> and report it; never silently narrow scope.

Run checks and update the ledger with:

node <this-skill-dir>/scripts/gate-check.mjs GATES.md

Use --status for a read-only ledger check. Keep gate files uncommitted unless the repository treats execution ledgers as project artifacts.

Choose the smallest mode

Solo, by default: one GATES.md, one coherent task, no orchestration.
Depth Tree: only for an explicit tree N request or work too large for one context. Read references/method.md, then create the plan and ledgers from templates/.
Orchestrated: only when the host permits subagents and fresh contexts materially help. Read references/orchestration.md, assign disjoint ownership, add branch integration gates, and have the parent rerun leaf checks. Respect the host's concurrency and delegation rules.

For long runs, consult references/token-economy.md and keep leaf briefs to their contract plus ledger.

Finish against evidence

Run the ledger checks and resolve every unmet gate.
Adversarially inspect at least one passed gate and correct weak evidence.
Remeasure every number used in the final report.
Report the met-gate count and every abandoned gate. Do not claim full completion when anything remains unmet.

Read the full file on GitHub · 61 lines

Files

What ships with it

11 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.

Changes

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 · 61 lines · 30 tokens per session scan A c4c34f4bf991

Subscribe to this mod's changes

unlazy is a skill published in the GitHub repository jkomyno/.dotfiles (5 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 564 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

unlazy