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 oleg494/coding-kit --skill incremental-implementationgit clone --depth 1 https://github.com/oleg494/coding-kitWrote 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/oleg494/coding-kit/incremental-implementation)<a href="https://agentmods.dev/skills/oleg494/coding-kit/incremental-implementation"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/incremental-implementation/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/oleg494/coding-kit/incremental-implementation"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/incremental-implementation.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.01159 |
| Opus 5.5 | $0.00018 | $0.00464 |
| Sonnet 5.5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
incremental-implementation 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 2d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incremental Implementation
Overview
Build in thin vertical slices — implement one piece, test it, verify it, then expand. Each increment should leave the system in a working, testable state.
When inline execution is appropriate, use the existing plan here task by task; this does not override a user-selected director mode or host delegation rules. Use the plan as the starting contract, resolving defects against user intent, current source and evidence. Scale final review to risk rather than mandating an implementer and reviewer per task. If subagents are unavailable, continue locally where possible; never fabricate a dispatch.
The Increment Cycle
Define check → Implement → Verify → Next slice → Integrated verification
For each slice:
- Implement the smallest complete piece of functionality
- Test — exercise the slice's affected behavior, reusing suitable checks
- Verify — confirm its observable result and relevant compatibility
- Move to the next slice without asking to continue already authorized work
An increment is an execution boundary, not permission to ship a partial request. Commits follow OPS.md §1; no automatic commit per slice.
Slicing Strategies
Vertical Slices (Preferred)
Build one complete path through the stack:
Slice 1: Create (DB + API + basic UI) → user can create
Slice 2: List (query + API + UI) → user can see
Slice 3: Edit (update + API + UI) → user can modify
Slice 4: Delete → full CRUD complete
Contract-First Slicing
Slice 0: Define API contract (types, interfaces)
Slice 1a: Implement backend against contract
Slice 1b: Implement frontend against the agreed contract
Slice 2: Integrate real backend and frontend, verify end-to-end
Risk-First Slicing
Tackle the riskiest piece first. If it fails, you discover it before investing in everything.
Implementation Rules
Rule 0: Simplicity First
Before writing code, ask: "What is the simplest thing that could work?"
Rule 0.5: Scope Discipline
Touch only what the task requires. Do NOT:
- "Clean up" adjacent code
- Refactor imports in files you're not modifying
- Add features not in the spec because they "seem useful"
- Modernize syntax in files you're only reading
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.
- 2d ago Changed · +36 lines 4659e96bffc7
- 9d ago Changed · -8 tokens per session 2f4d75f000e6
- 11d ago Changed 6adebc84ea28
- 25d ago Changed 6cc08553489c
- 26d ago Changed 05b891871723
- 1mo ago Changed c7083b8d10a6
- 1mo ago Changed · -2 lines 4d8c8fb61874
- 1mo ago Changed 286cc836db4f
- 1mo ago Changed 34ecb71e7779
- 1mo ago First seen · 96 lines · 52 tokens per session scan A 4886ccd54ab3
incremental-implementation is a skill published in the GitHub repository oleg494/coding-kit (3 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 1,159 once invoked, about $0.0002 per session on Opus 5.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
run
Execute a named agent role with optimized instructions. Explicit invocation only ($run). Never trigger implicitly.
tip
Deliver a transformative life perspective shift and a productivity tip. Use when the user invokes /tip or wants non-technical inspiration or a fresh mental model.
agentic-security-review
Run a security and dependency audit for agent systems, tool-using AI apps, MCP/A2A integrations, or security-sensitive AI-generated code. Check slopsquatting risk, tool shadowing, rug pulls, memory/context poisoning, secrets, unsafe permissions, and common CWE patterns. Use when asked for security review, dependency…
agentic-spec
Create a structured specification before agentic coding work. Assemble the six context types, scale rigor for prototype/internal/production tasks, produce SPEC.md, and configure focused AGENTS.md boundaries. Use when asked to write a spec, plan a feature, design an agent/system, define architecture, or create…
agentic-evals
Design evaluation contracts and test plans for agentic systems. Create deterministic tests, trajectory evals, quality dimensions, gold-set criteria, and CI gates before or after implementation. Use when asked for tests first, an eval plan, success criteria, non-deterministic testing, LLM-as-judge setup, or…
agentic-production-readiness
Prepare an AI agent system for production operation. Cover SHIELD controls, sandbox/canary/production rollout, OpenTelemetry observability with GenAI semantic conventions, Agent Card drafting, governance, and post-deploy monitoring. Use for production readiness checks, go-live checklists, agent monitoring, agent…