feature-impl

feature-impl is a skill for Claude Code, Codex from reboulip/rblclass. It costs 103 tokens per session (1,984 once invoked), scanned A, original, Apache-2.0.

A tool for implementing one planned RBLclass add-in task from start to finish. It follows an implementation brief, changes the required files, checks the result, and asks questions for verification.

In plain words
What is it for?
Use it to build a single feature, add its translations, verify the result, and update the add-in so it can be tested in Outlook.
Why use it?
It gives one roadmap task a defined workflow, reducing improvised changes and missed steps during development.

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/reboulip/rblclass/feature-impl
Any agent
npx skills add reboulip/rblclass --skill feature-impl
Clone the repo
git clone --depth 1 https://github.com/reboulip/rblclass

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.

agentmods badge for feature-impl

README.md
[![agentmods](https://agentmods.dev/badge/skills/reboulip/rblclass/feature-impl.svg)](https://agentmods.dev/skills/reboulip/rblclass/feature-impl)
Your own site
<a href="https://agentmods.dev/skills/reboulip/rblclass/feature-impl"><img src="https://agentmods.dev/badge/skills/reboulip/rblclass/feature-impl.svg" alt="Measured on agentmods" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,984 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.00103 $0.01984
Opus 5 $0.00051 $0.00992
Sonnet 5 $0.00021 $0.00397
Haiku 4.5 $0.00010 $0.00198

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

Security

Grade A, and why

feature-impl 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.

.claude/skills/feature-impl/SKILL.md · 173 lines

How it starts

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

/feature-impl — implement one sprint item end-to-end

Prerequisites

An Implementation Brief (produced by the feature-prep subagent) must be in the current conversation context. If one is not present, invoke it now:

Agent({
  subagent_type: "feature-prep",
  description: "Prepare implementation brief",
  prompt: "Sprint: [version]\nItem: [label] — [title]\n\n[full roadmap item text]"
})

Then continue once the brief is returned.

Step 1 — State the item

Before touching any file, state clearly which item you are implementing (e.g. "Implementing v2.4.0.0 A1 — Clear the search field after classify"). This anchors the conversation.

Step 2 — Implement

Work through each file in the brief's "Files to modify" and "Files to create" sections. Read the current file content (or the relevant section) before editing. Apply exactly the changes described in "Required changes" — no opportunistic refactoring of surrounding code.

Follow CLAUDE.md coding rules throughout: no comments unless the WHY is non-obvious, no extra abstractions, no error handling for impossible cases.

Step 3 — Localization

For every key listed in the brief's "Localization" section:

  • Add the key + English value to src/RBLclass.AddIn/Resources/Strings.resx.
  • Add translated values to Strings.fr.resx and Strings.de.resx.

ResourceParityTests fails the build if any key is missing or has mismatched {n} placeholders — never skip this step.

Step 4 — xUnit tests

For every test case in the brief's "xUnit tests" section:

  • Add it to the specified test class in tests/RBLclass.Core.Tests/.
  • Run dotnet test tests/RBLclass.Core.Tests/ --verbosity minimal and confirm all tests pass before proceeding.

Step 5 — Build check

msbuild is not on PATH on this machine — resolve it via vswhere first (same lookup Reload-Addin.ps1 uses), then build to catch compilation errors before reloading into Outlook:

$vswhere = "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe"
$msbuild = & $vswhere -latest -prerelease -products * -requires Microsoft.Component.MSBuild -find "MSBuild\**\Bin\MSBuild.exe" | Select-Object -First 1
if (-not $msbuild -or -not (Test-Path $msbuild)) { throw "MSBuild not found via vswhere." }
& $msbuild "src\RBLclass.AddIn\RBLclass.AddIn.csproj" /p:Configuration=Debug "/p:Platform=Any CPU" /t:Build /v:minimal /nologo

Read the full file on GitHub · 173 lines

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 · 173 lines · 0 tokens per session scan A 9f1561cc8773

Subscribe to this mod's changes

feature-impl is a skill published in the GitHub repository reboulip/rblclass (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,984 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens