Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add felvieira/claude-skills-fv/plugin install dev-team-kit-fvWrote 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/commands/felvieira/claude-skills-fv/drift-scan)<a href="https://agentmods.dev/commands/felvieira/claude-skills-fv/drift-scan"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/drift-scan/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/commands/felvieira/claude-skills-fv/drift-scan"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/drift-scan.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.00059 | $0.01027 |
| Opus 5 | $0.00030 | $0.00513 |
| Sonnet 5 | $0.00012 | $0.00205 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
drift-scan 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/drift-scan — Continuous Drift Detection
Objetivo: detectar drift gradual que os hooks no change-time (PreToolUse, PostToolUse) não pegam. Rodar contra todo o codebase periodicamente.
Inspirado em Birgitta Böckeler (Thoughtworks) — "continuous drift sensors that monitor what gradually accumulates: dead code, dependency staleness, test coverage degradation". Ver docs/inspiration/harness-engineering.md.
Sensores disponíveis
| Sensor | O que detecta | Custo |
|---|---|---|
large-files |
Arquivos > 400 linhas (configurável) | s |
dead-code |
Arquivos com exports sem importadores detectados | s-min |
stale-todos |
TODOs/FIXMEs > 90 dias (via git blame) | min |
dep-staleness |
Deps com major version atrasada (npm outdated) |
min |
doc-code-drift |
Docs referenciando arquivos que não existem mais | s |
test-coverage |
Arquivos sem teste correspondente | s |
Como invocar
/drift-scan # full scan, todos os sensores
/drift-scan --only large-files,stale-todos # apenas 2 sensores
/drift-scan --threshold-lines 500 # threshold custom
/drift-scan --format json # output JSON
Execute
Rode o script e mostre o output:
node "${CLAUDE_PLUGIN_ROOT}/scripts/drift-scan.mjs" $ARGUMENTS
Após o output, interprete os 3 maiores insights:
- Categoria com mais findings — sugerir próxima ação
- Finding crítico individual — se há finding de alta severity em arquivo central, destacar
- Tendência (se rodou antes) — comparar com scans anteriores se disponível
Quando rodar
- Semanal durante desenvolvimento ativo
- Antes de release (gate adicional além dos quality-gates normais)
- Após mergir branch grande (drift acumulado durante o branch)
- Sob suspeita — quando algo parece estranho mas você não sabe o quê
Pareando com outros comandos
| Finding | Próximo comando |
|---|---|
Muitos large-files |
/simplify ou /run-program refactor-safely |
Muitos dead-code |
Revisão manual (sensor pode ter false positives) — verificar dynamic imports antes de deletar |
Muitos stale-todos |
/auto pra resolver os críticos ou converter em issues |
dep-staleness com major bumps |
/run-program refactor-safely por dep |
doc-code-drift |
/auto para atualizar docs ou deletar referências |
| Pouca cobertura | Skill 05 (/test) ou skill 37 (TDD) |
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 · 89 lines · 59 tokens per session scan A e7a6439034dc
drift-scan is a command published in the GitHub repository felvieira/claude-skills-fv (23 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,027 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-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.