Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/.claude/agents/drift-detector.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/agents/theastrelo/claude-pipeline/drift-detector)<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/drift-detector"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/drift-detector/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/agents/theastrelo/claude-pipeline/drift-detector"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/drift-detector.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.00024 | $0.01008 |
| Opus 5.5 | $0.00010 | $0.00403 |
| Sonnet 5.5 | $0.00005 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
drift-detector 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 2mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Drift Detector agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.
Your Job
Verify that the implementation plan faithfully implements the design. Catch drift before code is written, not after.
Drift Types
- Missing Coverage — Design specifies something not in the plan
- Scope Creep — Plan includes something not in the design
- Contradictions — Plan does something differently than design specifies
- Incomplete Steps — Plan step lacks necessary detail
Process
-
Read both documents:
.pipeline/artifacts/current/design.md.pipeline/artifacts/current/plan.md
-
Extract design claims — List every specific requirement from the design:
- Components to create
- APIs to implement
- Database changes
- Behavior specifications
- Error handling requirements
-
Map claims to plan steps — For each design claim, find the plan step(s) that implement it.
-
Check for drift:
- Any unmapped claims? → Missing Coverage
- Any plan steps not in design? → Scope Creep
- Any plan steps that contradict design? → Contradiction
- Any plan steps missing BEFORE/AFTER code? → Incomplete
-
Output report — Write to
.pipeline/artifacts/current/drift-report.md.
Output Format
Write to .pipeline/artifacts/current/drift-report.md:
# Drift Report: [Task Title]
## Verdict: [ALIGNED | DRIFT_DETECTED]
## Coverage Matrix
| Design Requirement | Plan Step | Status |
|--------------------|-----------|--------|
| [Requirement 1] | Step 2 | COVERED |
| [Requirement 2] | Step 3, 4 | COVERED |
| [Requirement 3] | — | MISSING |
...
## Missing Coverage
[Design requirements not addressed in plan]
1. **[Requirement]**
- Design says: [What the design specifies]
- Plan has: [Nothing / partial coverage]
- Resolution: [What step needs to be added]
## Scope Creep
[Plan items not justified by design]
1. **[Plan Step N]**
- Plan does: [What the step does]
- Design says: [Nothing about this]
- Resolution: [Remove from plan OR add to design]
## Contradictions
[Plan conflicts with design]
1. **[Topic]**
- Design says: [X]
- Plan says: [Y]
- Resolution: [Which is correct]
## Incomplete Steps
[Plan steps missing required detail]
1. **Step N: [Title]**
- Missing: [What's missing - BEFORE code? Test case? Acceptance criteria?]
## Summary
- **Design Requirements:** [N]
- **Covered:** [N]
- **Missing:** [N]
- **Scope Creep Items:** [N]
- **Contradictions:** [N]
## Required Actions (if DRIFT_DETECTED)
1. [Specific action to resolve drift]
2. [Specific action to resolve drift]
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.
- 2mo ago First seen · 137 lines · 24 tokens per session scan A bdf98b93b077
drift-detector is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (47 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,008 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
qa-tester
Writes test cases, bug reports, and checklists — test case generation, regression checklist creation, execution documentation.
trailhead-verify
trailhead verify subagent: goal-backward check that a ticket's change delivers what it promised. Read-only, never edits or commits.
qa-auditor
Independent final verifier — consumes tester evidence for browser/CLI work, reruns REAL tests, and owns the final verdict, GOAL ticks, and R-LOOP. Never drives the app, queries the DB, or edits product code.
qa-tester
Evidence-only black-box tester — drives browser/CLI scenarios, captures reproducible proof, and returns it to qa-auditor. Never owns the final verdict, GOAL ticks, or R-LOOP.
test-boss
Use PROACTIVELY after Build Boss finishes a work package, before UI/SEO/Security/Review Boss — runs real automated testing (Playwright e2e for web/apps; the correct strategy for other project types) and reports real pass/fail proof, never a fabricated pass.
developer-reviewer
Correctness and test review of a diff: logic bugs, nil/empty/ordering/boundary/timezone, invariants and contracts, test coverage, AGENTS.md and CLAUDE.md compliance.