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 skills add dgalarza/claude-code-workflows --skill resolvegit 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/skills/dgalarza/claude-code-workflows/resolve)<a href="https://agentmods.dev/skills/dgalarza/claude-code-workflows/resolve"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/resolve/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/skills/dgalarza/claude-code-workflows/resolve"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.00919 |
| Opus 5.5 | $0.00006 | $0.00368 |
| Sonnet 5.5 | $0.00003 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
resolve 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-sentinel:resolve
Process accumulated drift warnings from .doc-sentinel-drift.json. For each warning, verify whether the doc actually drifted, fix it if so, or dismiss if it is a false positive.
Phase 1: Load Drift Queue
cat .doc-sentinel-drift.json 2>/dev/null || echo "No drift warnings pending"
If the file is empty or missing, report "No drift warnings to resolve" and exit.
Phase 2: Deduplicate and Group
Group warnings by doc file. Multiple source changes may affect the same doc — process them together for coherent updates.
Example grouping:
ARCHITECTURE.md
- src/routes/auth.ts changed (commit abc123)
- src/routes/users.ts changed (commit def456)
docs/api.md
- src/controllers/payments.ts changed (commit abc123)
Present the grouped summary and total count before proceeding.
Phase 3: Triage Each Group
For each doc file with drift warnings:
3a: Read Current State
Read the doc file and the changed source files to understand what actually changed.
3b: Classify the Drift
Determine what kind of drift occurred:
| Classification | Description | Action |
|---|---|---|
| Path moved | Source file was renamed or moved | Update path references in doc |
| API changed | Function signatures, endpoints, or interfaces changed | Update API documentation |
| Config changed | Env vars, ports, or settings changed | Update config references |
| Structure changed | Directories added/removed, module reorganized | Update codemap/architecture sections |
| Behavioral change | Logic changed but interface stayed the same | Update descriptions if they mention specific behavior |
| False positive | Doc references the file but the relevant content did not change | Dismiss |
3c: Apply Fix or Dismiss
For real drift:
- Read the doc section that references the changed code
- Read the new state of the source code
- Update the doc to reflect the current reality
- Keep the same writing style and level of detail as the surrounding content
- If unsure about intent, add a
<!-- TODO: verify -->comment rather than guessing
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 · 122 lines · 14 tokens per session scan A c06a7bdd4f72
resolve is a skill published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 919 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…