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 setupgit 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/setup)<a href="https://agentmods.dev/skills/dgalarza/claude-code-workflows/setup"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/setup/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/setup"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/setup.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.00022 | $0.00947 |
| Opus 5.5 | $0.00009 | $0.00379 |
| Sonnet 5.5 | $0.00004 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
setup 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-sentinel:setup
Interactive setup wizard that creates .doc-sentinel.json configuration.
Phase 1: Detect Project Layout
Run these commands to understand the project:
# Project structure
ls -la
ls docs/ 2>/dev/null || echo "No docs/ directory"
# Top-level doc files
for f in AGENTS.md ARCHITECTURE.md CLAUDE.md README.md CHANGELOG.md; do
[ -f "$f" ] && echo "Found: $f"
done
# Check for existing config
cat .doc-sentinel.json 2>/dev/null || echo "No existing config"
# Check for companion plugins
cat .doc-sync.json 2>/dev/null && echo "doc-sync detected"
cat .inkwell.json 2>/dev/null && echo "inkwell detected"
Phase 2: Discover Documentation Files
# Find all markdown docs
find . -name '*.md' -not -path './node_modules/*' -not -path './.git/*' | head -50
# Find source directories
ls -d src/ lib/ app/ packages/ */ 2>/dev/null | head -20
Phase 3: Configure
Build .doc-sentinel.json interactively. Present detected values and ask for confirmation.
Configuration Schema
{
"version": 1,
"docs_root": "docs",
"watch_files": [
"AGENTS.md",
"ARCHITECTURE.md",
"README.md"
],
"ignore_sources": [
"*.test.*",
"*.spec.*",
"__tests__/**",
"*.d.ts"
],
"ignore_docs": [],
"severity": {
"architecture": "high",
"agents_md": "high",
"api_reference": "medium",
"changelog": "low",
"readme": "medium"
}
}
Fields:
| Field | Type | Default | Purpose |
|---|---|---|---|
version |
number | 1 |
Config schema version |
docs_root |
string | "docs" |
Primary documentation directory |
watch_files |
string[] | ["AGENTS.md", "ARCHITECTURE.md", "README.md"] |
Additional doc files outside docs_root to monitor |
ignore_sources |
string[] | ["*.test.*", "*.spec.*", "__tests__/**", "*.d.ts"] |
Source file patterns to skip during drift detection |
ignore_docs |
string[] | [] |
Doc files to exclude from drift checks |
severity |
object | see below | Drift severity by doc category |
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 · 127 lines · 22 tokens per session scan A 1e6a6c954356
setup is a skill published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 947 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…