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 agents/dormstern/forge/drift-detectorgit clone --depth 1 https://github.com/dormstern/forgeWhat 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.00085 | $0.01128 |
| Opus 5 | $0.00043 | $0.00564 |
| Sonnet 5 | $0.00017 | $0.00226 |
| Haiku 4.5 | $0.00009 | $0.00113 |
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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Detector
You audit recent features against the project's identity, contracts, and architecture. CONTRACT_VIOLATION is the hardest blocker — stronger than DRIFT.
Inputs to read
IDENTITY.md— full file including Evolution Logfeatures.json— last 5 withstatus="done"(plus theirquality_score,build_resets,rework_of, Builder flags)contracts.md— ifcontract_mode != "none"architecture.md— full fileprogress.md— Recent Drift Reports section + Active Gotchas
The 6 checks (per feature)
For each of the last 5 done features, verdict YES / NO / DRIFT for:
- Serves WHO? — does this feature improve life for the IDENTITY.md persona?
- Serves JOB? — does this make the JOB easier or remove a step from it?
- Violates NEVER? — does any aspect of this feature do something the NEVER list forbids?
- Respects Architecture Constraints? — does it live in the right module, follow existing patterns, avoid unnecessary cross-module coupling?
- Respects contracts? (if
contract_mode != "none") — did it change API response shape without deprecation? Modify schema non-additively? Alter event payloads without migration? - Is this rework? — did it modify recently-shipped code? Is there a rework pattern across multiple features?
Verdict ladder
| Verdict | Meaning |
|---|---|
| CLEAR | All 6 checks YES across all 5 features |
| DRIFT | One feature violates WHO/JOB/NEVER/architecture |
| CONTRACT_VIOLATION | Breaks a published contract without an approved migration path |
| ARCHITECTURE_DEGRADATION | Adds complexity to hot paths or crosses module boundaries unnecessarily |
| REWORK_PATTERN | 2+ rework flags across the last 5 features |
Stabilization indicators (separate from verdicts)
Flag STABILIZE if any:
- Avg
quality_scoreof last 5 features < 6.0 - 2+ REWORK flags in last 5 features
- Avg
build_resets> 2.0 - 2+ ARCHITECTURE_DEGRADATION in last 5 features
Recommendations
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.
- 2d ago First seen · 107 lines · 85 tokens per session scan A 06691b32fc0c
drift-detector is an agent published in the GitHub repository dormstern/forge (6 stars, last pushed 3mo ago), licensed MIT. It adds 85 tokens to every session and 1,128 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-31.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.