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 agentmods add skills/matteocervelli/llms/implementationnpx skills add matteocervelli/llms --skill implementationgit clone --depth 1 https://github.com/matteocervelli/llmsWhat 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 | $0.00027 | $0.03552 |
| Opus 5 | $0.00014 | $0.01776 |
| Sonnet 5 | $0.00005 | $0.00710 |
| Haiku 4.5 | $0.00003 | $0.00355 |
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 today.
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 — 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
)
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.
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.
- today First seen · 725 lines · 27 tokens per session scan A 935508559029
implementation is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 3,552 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.