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.
git clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/shipwithai/shipwithai-plugins/drift-monitor)<a href="https://agentmods.dev/agents/shipwithai/shipwithai-plugins/drift-monitor"><img src="https://agentmods.dev/badge/agents/shipwithai/shipwithai-plugins/drift-monitor/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/shipwithai/shipwithai-plugins/drift-monitor"><img src="https://agentmods.dev/badge/agents/shipwithai/shipwithai-plugins/drift-monitor.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.00067 | $0.00700 |
| Opus 5 | $0.00034 | $0.00350 |
| Sonnet 5 | $0.00013 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
drift-monitor 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 12d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Monitor
Purpose
Detects when CLAUDE.md, docs/ARCHITECTURE.md, and plugin READMEs fall out of sync with the actual repository state. Prevents stale documentation from misleading future Claude sessions.
Context
Reads on startup:
CLAUDE.md— declared project structure and conventionsdocs/ARCHITECTURE.md— declared architecture and key directoriesplugins/*/manifest.json— declared skill registry per pluginplugins/*/README.md— plugin-level documentationplugins/*/plugin.json— plugin metadata (name, version)
Steps
Step 1 — Scan actual state
Read the real directory tree:
- List all
plugins/*/directories - For each plugin: list
skills/subdirectories and compare againstmanifest.json - Check
plugins/*/README.mdandplugins/*/CHANGELOG.mdfor last-updated markers - Check
plugins/*/plugin.jsonversion againstCHANGELOG.mdlatest entry
Step 2 — Compare against CLAUDE.md
Check each section of CLAUDE.md for accuracy:
- Key directories — do the listed paths actually exist?
- Sensitive areas — are the listed paths still present?
- Conventions — do named tools/patterns match what's in the repo?
- Harness config — does Tier/Last updated reflect current state?
Step 3 — Compare against docs/ARCHITECTURE.md
- Key layers table — do the listed directories exist?
- Entry points — are
manifest.jsonfiles where declared? - Key directories tree — does it match
find plugins/ -maxdepth 3 -type d?
Step 4 — Check plugin SSOT
For each plugin directory:
- Does
README.mdlist all skills currently inskills/? - Does
manifest.jsonlist all skills inskills/(no extras, no missing)? - Does
CHANGELOG.mdhave an entry for the current version inplugin.json?
Step 5 — Report
Produce a drift report:
## Drift Report — [DATE]
### ✅ In sync
- [item that matches]
### ⚠️ Drifted
- [file/section]: declared "[X]" but actual state is "[Y]"
→ Suggested fix: [one-line fix]
### ❌ Missing
- [file/section that is declared but does not exist]
→ Suggested fix: [one-line fix]
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.
- 12d ago First seen · 86 lines · 67 tokens per session scan A 7ff564bb9866
drift-monitor is an agent published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 29d ago), licensed MIT. It adds 67 tokens to every session and 700 once invoked, about $0.0003 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
code-quality-plan-creator-default
Architectural Code Quality Agent (LSP-Powered) - Creates comprehensive architectural improvement plans suitable for loop or swarm executors (/implement-loop, /tasks-loop or /tasks-swarm, /beads-loop or /beads-swarm). Uses Claude Code's built-in LSP for semantic code understanding. This agent thoroughly analyzes code…
beads-converter-default
Verbatim plan-to-beads converter using the bd CLI. Copies full implementation code, requirements, and exit criteria directly into each bead. Each bead is 100% self-contained - no plan back-references or external lookups needed.
bug-plan-creator-default
Architectural Bug Investigation Agent. Deep investigation with line-by-line code analysis, produces fix plans with exact code changes, regression prevention, and verification criteria. Plans work with any executor (loop or swarm).
codemap-creator-default
Generate or update hierarchical code maps using LSP. Two modes: create (full scan from root) and update (re-scan only changed files from git diff, MR, or PR). Maps show directory tree with symbols, signatures, dependencies, and export status. Consumed by /plan-creator for codebase orientation.
plan-creator-default
Architectural Planning Agent for Brownfield Development. Creates plans for new features with exact code structures, per-file implementation details, and dependency graphs. Plans work with any executor (loop or swarm). For bugs use bug-plan-creator, for code quality use code-quality-plan-creator.
document-creator-default
Generate DEVGUIDE.md architectural documentation using LSP for symbol extraction and pattern analysis. Creates .claude/rules/ files when missing. ONLY creates documentation - does not edit existing docs.