Borrowing it
Nothing to install: this file belongs to mick-gsk/drift. 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/mick-gsk/drift/main/.github/skills/drift-evidence-artifact-authoring/SKILL.mdgit clone --depth 1 https://github.com/mick-gsk/driftWrote 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/mick-gsk/drift/drift-evidence-artifact-authoring)<a href="https://agentmods.dev/skills/mick-gsk/drift/drift-evidence-artifact-authoring"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-evidence-artifact-authoring/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.
<a href="https://agentmods.dev/skills/mick-gsk/drift/drift-evidence-artifact-authoring"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-evidence-artifact-authoring.svg" alt="Reviewed on agentmods" width="80" 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.00108 | $0.03210 |
| Opus 5 | $0.00054 | $0.01605 |
| Sonnet 5 | $0.00022 | $0.00642 |
| Haiku 4.5 | $0.00011 | $0.00321 |
Grade A, and why
drift-evidence-artifact-authoring 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 11d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Evidence Artifact Authoring Skill
Dieser Skill produziert ein vollständiges, commit-readies vX.Y.Z_<feature-slug>_feature_evidence.json in benchmark_results/.
Wann Verwenden
feat:commit geplant unddrift-commit-pushbeanstandet fehlendes Evidence-File- Neues Signal oder materielle Heuristikänderung abgeschlossen
- Precision-/Recall-Änderung > 5 Prozentpunkte vorhanden und zu belegen
- Signal-Fix oder FP-Reduktion mit empirischen Belegen versehen
Pflicht-Vorbedingungen
- Tests laufen durch (
make test-fastgrün) - ADR vorhanden oder Entscheidung explizit als fix/refactor eingestuft
- Version aus
pyproject.tomloder geplanter nächster Version bekannt git diff --statzeigt, welche Dateien tatsächlich geändert wurden
Step 1: Evidence-Datei deterministisch generieren (PRIMÄRE METHODE)
Ab Gate 2b ist manuelles Erstellen von Evidence-Dateien für neue feat:-Commits nicht
zulässig. Der Pre-Push-Hook verifiziert, dass die Datei maschinell erzeugt wurde.
Befehl:
python scripts/generate_feature_evidence.py --version X.Y.Z --slug my-feature
Das Script:
- Läuft
drift analyze --repo . --format json --exit-zero→ erfasstdrift_score,total_findings - Läuft
pytest tests/ -q --tb=short -m not slow -n auto→ erfassttotal_passing,total_failing - Läuft
pytest tests/test_precision_recall.py→ erfasst Precision/Recall (optional via--skip-precision-recall) - Bettet einen
generated_by-Block mitgit_sha, Timestamp und Script-Name ein - Schreibt
benchmark_results/vX.Y.Z_{slug}_feature_evidence.json
Flags:
--version X.Y.Z Semver-Version (Pflicht)
--slug my-feature Kebab-Case-Slug (Pflicht)
--feature "Text" Kurzbeschreibung (optional, Default: Slug)
--skip-tests Nur Self-Analysis (kein pytest)
--skip-precision-recall Precision-Recall-Suite überspringen
Validierung manuell prüfen:
python scripts/validate_feature_evidence.py \
benchmark_results/vX.Y.Z_my-feature_feature_evidence.json \
--require-generated-by --push-head $(git rev-parse HEAD)
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.
- 11d ago First seen · 343 lines · 108 tokens per session scan A 40b8e0a97296
drift-evidence-artifact-authoring is a skill published in the GitHub repository mick-gsk/drift (15 stars, last pushed 1mo ago), licensed MIT. It adds 108 tokens to every session and 3,210 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.
Other skills, from other repositories
contract-derivation
Use this skill after a design document exists and before any module is implemented. It takes a design doc and derives per-module contracts (manifests) that are complete enough for an implementor working in isolation to build each module correctly without seeing the rest of the system. Trigger this whenever the user…
design-doc
Use this skill before writing any non-trivial code, especially when starting a new feature, service, or codebase. It produces a structural design document that commits to module boundaries, contracts, and data shapes BEFORE implementation begins. Trigger this whenever the user describes building something new, asks to…
dispatcher
Use this skill when running a Taniwha build from the main Claude Code session. The skill turns the main session into a thin, mechanical executor that follows instructions from ephemeral orchestrator subagents. Trigger this whenever the user wants to start a Taniwha build, resume an interrupted one, or work on a…
verifier
Use this skill when verifying that a completed Taniwha implementation or composition satisfies its contract's acceptance criteria. The verifier reads the contract, the implementation's source files, and the project context, then writes its own tests against the contract's acceptance criteria, runs them, and reports…
composition
Use this skill when wiring two completed modules together to satisfy a parent contract, especially in a compartmentalised setting. Trigger this whenever the user has two implemented modules (each with its manifest) and a parent contract that says how they should compose, when the user asks to "compose these modules"…
leaf-implementation
Use this skill when implementing a single module against a contract manifest, especially in a compartmentalised setting where the implementor should NOT see the rest of the system. Trigger this whenever a manifest exists and the user wants to implement that module, asks to "implement this module", "build against this…