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-signal-development-full-lifecycle/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-signal-development-full-lifecycle)<a href="https://agentmods.dev/skills/mick-gsk/drift/drift-signal-development-full-lifecycle"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-signal-development-full-lifecycle/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-signal-development-full-lifecycle"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-signal-development-full-lifecycle.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.00079 | $0.01668 |
| Opus 5 | $0.00039 | $0.00834 |
| Sonnet 5 | $0.00016 | $0.00334 |
| Haiku 4.5 | $0.00008 | $0.00167 |
Grade A, and why
drift-signal-development-full-lifecycle 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Signal Development Full Lifecycle Skill
Use this skill for non-trivial signal work from decision through validation.
When To Use
- A new signal is being added
- An existing signal changes materially
- A signal heuristic is recalibrated in a way that affects trust, precision, or recall
- A signal is being prepared for scoring readiness or report-only hardening
Core Rules
- Run the Drift Policy Gate first. Signal work that fails admissibility should stop before design begins.
- ADR before implementation. Non-trivial signal work needs an ADR draft before code changes.
- Every signal must be explicit about scope. Declare
incremental_scopeon the class. - Evidence is mandatory. Signal logic without fixtures, targeted tests, and audit updates is incomplete.
- Optimize for credibility before comfort. Precision, reproducibility, and actionability outrank convenience or breadth.
Step 0: Run The Drift Policy Gate
Use the gate format from .github/instructions/drift-policy.instructions.md before doing design or implementation work.
Step 1: Start With Decision And Design
Before coding:
- decide whether the task is a new signal, a material heuristic change, or a calibration pass
- draft or update the ADR using the
drift-adr-workflowskill - use
docs/decisions/templates/signal-design-template.mdfor signal-centric decisions
If a calibration materially changes signal behavior, scoring implications, or reviewer trust expectations, treat it as ADR-worthy even when it is framed as precision/recall hardening.
The design should already state:
- the problem class
- heuristic outline
- expected FP classes
- expected FN classes
- fixture plan
- validation criterion
Step 2: Implement The Signal Class Correctly
New signal code belongs in its own file under src/drift/signals/. For changes to an existing signal, keep the work in that signal's existing file unless there is a separately justified design change.
Implement the class as a BaseSignal subclass and register it with @register_signal.
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 · 189 lines · 79 tokens per session scan A 8e78efe10da0
drift-signal-development-full-lifecycle is a skill published in the GitHub repository mick-gsk/drift (15 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,668 once invoked, about $0.0004 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
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…
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…
refactoring-workflow
Improve the structure of existing code without changing its behaviour, in small verified steps under a green test suite. Use when the user asks to refactor, clean up, restructure or simplify code, wants to reduce duplication or coupling, is preparing a codebase for a feature it cannot currently accommodate, or when…
ralphctl-test-driven-development
Execute-phase skill — write the failing test before the code that makes it pass; for bug fixes, this is the reproduction test itself. Use for any logic change, bug fix, or behavioural modification; for the full root-cause triage pipeline around an unexpected failure, see ralphctl-debugging-and-error-recovery.
layer-check
Three-Layer Enforcement - Production Reality Gate.
gate-keeper
Rigorous quality guardian with auto-fix capability.