Borrowing it
Nothing to install: this file belongs to matteocervelli/llms. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/matteocervelli/llms/main/.claude/skills/test-scaffold/SKILL.mdgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/test-scaffold)<a href="https://agentmods.dev/skills/matteocervelli/llms/test-scaffold"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/test-scaffold.svg" alt="Measured on agentmods" 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.00069 | $0.01393 |
| Opus 5 | $0.00034 | $0.00696 |
| Sonnet 5 | $0.00014 | $0.00279 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
test-scaffold 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Scaffold Skill
Purpose
Generate unit test files with proper structure, fixtures, and mocking patterns. Auto-detects framework (pytest vs Jest) based on project configuration.
Quick Start
/test-scaffold <source-file>
Framework Detection
- Check for
pytest.ini,pyproject.toml [tool.pytest]-> pytest - Check for
jest.config.*,package.json jest-> Jest - File extension:
.py-> pytest,.ts/.js-> Jest
Test File Naming
| Source | Test File |
|---|---|
src/utils/validator.py |
tests/test_validator.py |
src/utils/validator.ts |
src/utils/validator.test.ts |
src/components/Button.tsx |
src/components/Button.test.tsx |
Test Structure (AAA Pattern)
All tests follow Arrange-Act-Assert:
def test_function_condition_expected():
# Arrange - setup state
input_data = {"key": "value"}
# Act - execute behavior
result = function_under_test(input_data)
# Assert - verify outcome
assert result.success is True
Pytest Template
"""Tests for [module_name]."""
import pytest
from unittest.mock import Mock, patch
from src.module import function_to_test, ClassToTest
@pytest.fixture
def sample_data():
"""Sample test data."""
return {"id": 1, "name": "test"}
@pytest.fixture
def mock_dependency():
"""Mock external dependency."""
mock = Mock()
mock.method.return_value = {"status": "ok"}
return mock
class TestClassName:
"""Tests for ClassName."""
def test_init_valid_params(self):
"""Test initialization with valid params."""
instance = ClassToTest(param="value")
assert instance.param == "value"
def test_method_returns_expected(self, sample_data):
"""Test method returns expected result."""
instance = ClassToTest()
result = instance.method(sample_data)
assert result["processed"] is True
def test_function_happy_path(sample_data):
"""Test function with valid input."""
result = function_to_test(sample_data)
assert result is not None
def test_function_none_raises():
"""Test function raises on None input."""
with pytest.raises(ValueError, match="cannot be None"):
function_to_test(None)
@pytest.mark.parametrize("input_val,expected", [
("valid", True),
("invalid", False),
("", False),
])
def test_validation_cases(input_val, expected):
"""Test validation with multiple inputs."""
assert validate(input_val) == expected
@patch("src.module.external_api")
def test_with_mocked_api(mock_api):
"""Test with mocked external API."""
mock_api.return_value = {"data": "test"}
result = function_using_api()
assert result["data"] == "test"
mock_api.assert_called_once()
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.
- 3d ago First seen · 249 lines · 69 tokens per session scan A 0217c6fdea06
test-scaffold is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,393 once invoked, about $0.0003 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-03.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.