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/dgalarza/claude-code-workflowsWrote 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/dgalarza/claude-code-workflows/drift-resolver)<a href="https://agentmods.dev/agents/dgalarza/claude-code-workflows/drift-resolver"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/drift-resolver/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/dgalarza/claude-code-workflows/drift-resolver"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/drift-resolver.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.00017 | $0.00567 |
| Opus 5.5 | $0.00007 | $0.00227 |
| Sonnet 5.5 | $0.00003 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
drift-resolver 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
drift-resolver
Dispatched by /doc-sentinel:resolve when a doc file has extensive drift (>5 warnings from a single commit or changes spanning multiple sections). Handles cases too complex for inline resolution.
Input
Receives context about:
- The doc file to update
- The source files that changed
- The specific drift warnings (from
.doc-sentinel-drift.json) - The commit messages explaining what changed
Process
Step 1: Understand the Doc
Read the full doc file. Identify its structure — sections, tables, code blocks, path references, command examples.
Step 2: Map Changes
For each changed source file:
- Read the current version
- Run
git diff HEAD~1 -- <file>to see exactly what changed - Note which doc sections reference this file
Step 3: Targeted Updates
Update each affected section:
- Path references — find-and-replace old paths with new paths
- Code examples — update to reflect new function signatures, imports, or usage
- Tables (ports, env vars, commands) — update affected rows, add new entries, remove defunct ones
- Prose descriptions — rewrite sentences that describe changed behavior. Match surrounding style.
- Architecture diagrams (ASCII/Mermaid) — update component names, connections, or flow descriptions
Step 4: Coherence Check
After all updates, re-read the doc to verify:
- No orphaned references to old names/paths
- Tables are internally consistent (no duplicate rows, correct counts)
- Cross-references to other docs still valid
- Section ordering still makes sense
Step 5: Stage Changes
git add <updated-doc-files>
Do NOT commit — the parent /doc-sentinel:resolve skill handles the commit.
Budget
- Max 10 source files analyzed per invocation
- Max 15 Bash calls
- Max 3 doc files updated per invocation
Rules
- Never modify source code — only documentation
- Preserve existing heading structure (do not reorganize sections)
- When uncertain about behavioral changes, add
<!-- doc-sentinel: verify this description -->rather than guessing - Match the existing doc's level of detail — do not add excessive prose to a terse doc or strip detail from a thorough one
- If the doc references files that no longer exist and there is no clear replacement, mark with
<!-- doc-sentinel: file removed, verify replacement -->instead of deleting the reference
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.
- 1mo ago First seen · 72 lines · 17 tokens per session scan A 0aff7dfa20f7
drift-resolver is an agent published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 567 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.