Claude-Pipeline: Agent for Claude Code

.claude/agents/drift-detector.md

drift-detector is an agent for Claude Code from TheAstrelo/Claude-Pipeline. It costs 24 tokens per session (1,008 once invoked), scanned A, original, MIT.

An add-on for making, testing, exporting, and deploying games with Godot 4, a game-development engine. It covers GDScript tests inside Godot and Python-based automated tests outside it.

In plain words
What is it for?
Use it to build Godot games, run unit or end-to-end tests, export web or desktop versions, and deploy web builds to services such as Vercel, GitHub Pages, or itch.io.
Why use it?
It brings game development, testing, and release steps into one workflow. This helps catch problems before exporting and reduces manual steps when publishing a game.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is TheAstrelo/Claude-Pipeline's own configuration. It tells Claude Code how to work on Claude-Pipeline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Pipeline configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/TheAstrelo/Claude-Pipeline/main/.claude/agents/drift-detector.md
Clone the repo
git clone --depth 1 https://github.com/TheAstrelo/Claude-Pipeline

Made for: Claude Code.

Wrote 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.

agentmods badge for drift-detector

README.md
[![agentmods](https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/drift-detector.svg)](https://agentmods.dev/agents/theastrelo/claude-pipeline/drift-detector)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,008 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.01008
Opus 5 $0.00012 $0.00504
Sonnet 5 $0.00005 $0.00202
Haiku 4.5 $0.00002 $0.00101

Measured 8d ago against content hash bdf98b93b077, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 8d 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.

.claude/agents/drift-detector.md · 137 lines

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

  1. Missing Coverage — Design specifies something not in the plan
  2. Scope Creep — Plan includes something not in the design
  3. Contradictions — Plan does something differently than design specifies
  4. Incomplete Steps — Plan step lacks necessary detail

Process

  1. Read both documents:

    • .pipeline/artifacts/current/design.md
    • .pipeline/artifacts/current/plan.md
  2. Extract design claims — List every specific requirement from the design:

    • Components to create
    • APIs to implement
    • Database changes
    • Behavior specifications
    • Error handling requirements
  3. Map claims to plan steps — For each design claim, find the plan step(s) that implement it.

  4. 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
  5. 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]

Read the full file on GitHub · 137 lines

Changes

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.

  1. 8d ago First seen · 137 lines · 24 tokens per session scan A bdf98b93b077

Subscribe to this mod's changes

drift-detector is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (44 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 1,008 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

developer-reviewer

Correctness and test review of a diff: logic bugs, nil/empty/collection-ordering/boundary/timezone, invariants and contracts, test coverage (red to green), AGENTS.md / CLAUDE.md compliance. Two gates: PLAN (risk and test plan) and VERIFY (adversarial diff review). Read-only; returns findings with severity and a fix.…

waqas1412/claude-harness · 199 tokens

gamedev-qa-tester

You are a QA Tester for an indie game project. You write thorough test cases and detailed bug reports that enable efficient bug fixing and prevent regressions. You also write automated test stubs and understand engine-specific test patterns — when a story needs a GDScript/C#/C++ test file, you can scaffold it.

FluxonLab/Skillry · 48 tokens

gamedev-qa-lead

You are the QA Lead for an indie game project. You ensure the game meets quality standards through systematic testing, bug tracking, and release readiness evaluation. You practice shift-left testing — QA is involved from the start of each sprint, not just at the end. Testing is a hard part of the Definition of Done…

FluxonLab/Skillry · 52 tokens

test-auditor

Detects fake, theatrical, and meaningless tests. Use PROACTIVELY after test suites are written to catch mock-everything tests, tautological assertions, happy-path-only coverage, and tests that pass but verify nothing. The anti-"test theater" agent.

elixpo/claudeOps.elixpo · 58 tokens

fuzzer

Generates property-based tests that find edge cases humans miss. Use for pure functions, parsers, serializers, data transformations, and any code where input space is large.

elixpo/claudeOps.elixpo · 37 tokens

qa-tester

The QA Tester writes detailed test cases, bug reports, and test checklists. Use this agent for test case generation, regression checklist creation, bug report writing, or test execution documentation.

Donchitos/Claude-Code-Game-Studios · 41 tokens