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 skills/dgalarza/claude-code-workflows/resolvenpx skills add dgalarza/claude-code-workflows --skill resolvegit clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWhat 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.00014 | $0.00919 |
| Opus 5 | $0.00007 | $0.00460 |
| Sonnet 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 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 — 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.
- 2d 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 (59 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 919 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…