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/lantisprime/claude-sdlc/testnpx skills add lantisprime/claude-sdlc --skill testgit clone --depth 1 https://github.com/lantisprime/claude-sdlcWrote 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/lantisprime/claude-sdlc/test)<a href="https://agentmods.dev/skills/lantisprime/claude-sdlc/test"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/test.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 | $0.00097 | $0.00832 |
| Opus 5 | $0.00048 | $0.00416 |
| Sonnet 5 | $0.00019 | $0.00166 |
| Haiku 4.5 | $0.00010 | $0.00083 |
Grade A, and why
test 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test (Phase 5)
Execute the tests defined in Design, report results, route defects.
Prerequisite
.claude/sdlc/gates/build-<task-slug>.md must exist and be signed.
Step 1 — Execute functional tests
Run the test runner configured in config/tools.json. Capture:
- Pass/fail per test case (tied back to REQ IDs via the test-case metadata)
- Coverage (vs. configured threshold; default 80% on modified code)
- Duration, flakiness if observed
Write the execution report to .claude/sdlc/test/<task-slug>-report.md.
Step 2 — Log defects
For each failure, create a defect record:
- If Git + Issues detected (per
.claude/sdlc/env.json): create an issue with labelsdefect,severity:<level>,phase:test, and link to the test case and REQ IDs. - Otherwise: write
.claude/sdlc/defects/<task-slug>/<defect-id>.mdusingtemplates/defect.md. Use JSON ifartifact_format_fallbackis set tojson.
Every defect references at least one REQ ID and at least one test case.
Step 3 — UX conformance
If the build produced frontend output, run the UX conformance checklist:
- Visual comparison against mockups (screenshots under
.claude/sdlc/test/ux/<task-slug>/) - Spacing, palette, typography, component usage, state handling
- Accessibility basics (contrast, keyboard nav, ARIA)
Record pass/fail items in the report. UX failures are defects, logged the same way.
Step 4 — Coverage gate
If coverage on modified code is below threshold, the phase fails. Either:
- Add missing tests (but only for modified functions — see Phase 4 rule), or
- Record an explicit waiver in the report with justification, requiring human gate to accept.
Human gate
Summarize: tests run, pass/fail, coverage on modified code, defects logged, UX status. Sign-off → .claude/sdlc/gates/test-<task-slug>.md.
What this skill must NOT do
- Do not silently skip failing tests.
- Do not inflate coverage by adding tests for unmodified code.
- Do not mark a UX failure as "cosmetic" without human confirmation.
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 · 83 lines · 97 tokens per session scan A 74a456af6a4a
test is a skill published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 4mo ago), licensed MIT. It adds 97 tokens to every session and 832 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-31.
Other skills, from other repositories
weather-fetcher
Instructions for fetching current weather temperature data for Dubai, UAE from Open-Meteo API.
LQF_Machine_Learning_Expert_Guide
LQF Machine Learning Expert Guide - Routed skill for ML/Statistical Modeling with Critical Discussion Mode. Triggers on: machine learning, modeling, prediction, training, classification, regression, clustering, deep learning, neural network, model evaluation, feature engineering, hyperparameter tuning, overfitting…
clinpgx-database
Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.
alpha-vantage
Access real-time and historical stock market data, forex rates, cryptocurrency prices, commodities, economic indicators, and 50+ technical indicators via the Alpha Vantage API. Use when fetching stock prices (OHLCV), company fundamentals (income statement, balance sheet, cash flow), earnings, options data, market…
datavis
Comprehensive data visualization toolkit for creating beautiful, mathematically elegant visualizations with D3.js, Chart.js, and custom SVG. Use when (1) building interactive data visualizations, (2) designing color palettes for charts, (3) choosing scales and visual encodings, (4) creating data pipelines from…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…