implementation

implementation is a skill for Claude Code from matteocervelli/llms. It costs 27 tokens per session (3,552 once invoked), scanned A, original, MIT.

A guide for implementing software features with code, tests, and documentation while following project standards. It also explains TDD, a method of writing tests before the implementation.

In plain words
What is it for?
It is for setting up development work, using the red-green-refactor testing cycle, writing tests, implementing code, and recording technical decisions.
Why use it?
It gives a structured path from an approved design to a tested and documented feature.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit It is for setting up development work, using the red-green-refactor testing cycle, writing tests, implementing code, and recording technical decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/matteocervelli/llms/implementation
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 matteocervelli/llms --skill implementation
Clone the repo
git clone --depth 1 https://github.com/matteocervelli/llms

Made for: Claude Code.

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 implementation

README.md
[![agentmods](https://agentmods.dev/badge/skills/matteocervelli/llms/implementation/github.svg)](https://agentmods.dev/skills/matteocervelli/llms/implementation)
Your own site
<a href="https://agentmods.dev/skills/matteocervelli/llms/implementation"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/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.

agentmods 80×15 button for implementation

Your own site · 80×15
<a href="https://agentmods.dev/skills/matteocervelli/llms/implementation"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,552 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.03552
Opus 5.5 $0.00011 $0.01421
Sonnet 5.5 $0.00005 $0.00710
Haiku 4.5 $0.00003 $0.00355

Measured 1mo ago against content hash 935508559029, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/generate_tests.py), 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.

.archive/builders/tools/skill_builder/templates/implementation/SKILL.md · 725 lines

How it starts

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

Feature Implementation Skill

Purpose

This skill provides systematic guidance for implementing features with high-quality code, comprehensive tests, and proper documentation, following project standards and best practices.

When to Use

  • After design phase is complete and approved
  • Need to implement code for a feature
  • Writing unit and integration tests
  • Creating technical documentation
  • Following TDD (Test-Driven Development) workflow

Implementation Workflow

1. Setup and Preparation

Review Design Document:

  • Read architecture design from previous phase
  • Understand component structure
  • Review API contracts and data models
  • Note security and performance requirements

Setup Development Environment:

# Activate virtual environment
source venv/bin/activate  # or: uv venv && source .venv/bin/activate

# Install dependencies
pip install -r requirements.txt
# or: uv pip install -r requirements.txt

# Install dev dependencies
pip install -e ".[dev]"

Create Feature Branch:

git checkout -b feature/feature-name

Deliverable: Development environment ready


2. Test-Driven Development (TDD)

TDD Cycle: Red → Green → Refactor

Step 1: Write Failing Test (Red)

# tests/test_feature.py
import pytest
from feature import process_data

def test_process_data_success():
    """Test successful data processing."""
    # Arrange
    input_data = {"name": "test", "value": 123}

    # Act
    result = process_data(input_data)

    # Assert
    assert result.name == "test"
    assert result.value == 123

Step 2: Write Minimal Code (Green)

# src/tools/feature/core.py
def process_data(input_data: dict):
    """Process input data."""
    # Minimal implementation to pass test
    return type('Result', (), input_data)()

Step 3: Refactor (Refactor)

# src/tools/feature/core.py
from .models import InputModel, ResultModel

def process_data(input_data: dict) -> ResultModel:
    """
    Process input data and return result.

    Args:
        input_data: Input data dictionary

    Returns:
        ResultModel with processed data

    Raises:
        ValidationError: If input is invalid
    """
    # Proper implementation with validation
    validated = InputModel(**input_data)
    return ResultModel(
        name=validated.name,
        value=validated.value
    )

Read the full file on GitHub · 725 lines

Files

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.

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. 1mo ago First seen · 725 lines · 27 tokens per session scan A 935508559029

Subscribe to this mod's changes

implementation is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 3,552 once invoked, about $0.0001 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-09-01.