implement-feature

A development workflow for implementing a software feature from its design document and adding tests for it.

In plain words
What is it for?
Use it when a feature has already been designed and needs to be built and verified with tests.
Why use it?
It helps turn written requirements into working, checked code instead of leaving testing and implementation decisions unclear.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/janekbaraniewski/openusage/implement-feature
Any agent
npx skills add janekbaraniewski/openusage --skill implement-feature
Clone the repo
git clone --depth 1 https://github.com/janekbaraniewski/openusage

Made for: Claude Code, Codex.

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 61 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00061
Opus 5 $0.00006 $0.00030
Sonnet 5 $0.00002 $0.00012
Haiku 4.5 $0.00001 $0.00006

Measured 3d ago against content hash 86ca7447c4c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-feature 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 3d 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.

.codex/skills/implement-feature/SKILL.md · 11 lines

What it actually says

Skill: Implement Feature

Invocation: Implement a feature from its design doc with tests

Read and follow the full skill specification in docs/skills/implement-feature/SKILL.md.

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.

  1. 3d ago First seen · 11 lines · 12 tokens per session scan A 86ca7447c4c3

Subscribe to this mod's changes

implement-feature is a skill published in the GitHub repository janekbaraniewski/openusage (180 stars, last pushed 9d ago), licensed MIT. It adds 12 tokens to every session and 61 once invoked, about $0.0001 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-30.