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/agent-readynpx skills add dgalarza/claude-code-workflows --skill agent-readygit 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.00100 | $0.08843 |
| Opus 5 | $0.00050 | $0.04422 |
| Sonnet 5 | $0.00020 | $0.01769 |
| Haiku 4.5 | $0.00010 | $0.00884 |
Grade A, and why
agent-ready 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 — 713 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-Ready
Scaffold the documentation and structural artifacts that make a codebase legible to AI agents. This skill is the remediation companion to codebase-readiness -- it does not score, it builds.
Startup: Check for Prior Assessment
Before entering any mode, check if AGENT_READY_ASSESSMENT.md exists in the project root.
If it exists:
- Read it and extract dimension scores
- Auto-suggest a mode based on the weakest dimensions:
- Documentation & Context < 50 -> suggest claude-md first
- Architecture Clarity < 50 -> suggest architecture first
- Both < 50 -> suggest scaffold (full setup)
- Quality gates at L0-L2 in the snapshot (or Code Clarity / Change Safety < 50 with no debt gate in the evidence) -> suggest quality-gates
- Tell the user: "I found an existing assessment. Based on your scores, I recommend starting with [mode]. Want to proceed, or choose a different mode?"
If it does not exist, proceed with mode detection.
Mode Detection
Determine which mode to run based on user intent:
| User Intent | Mode | Trigger Phrases |
|---|---|---|
| Full documentation setup | scaffold | "make this agent-ready", "full setup", "scaffold docs" |
| Generate architecture doc | architecture | "create ARCHITECTURE.md", "architecture doc", "codemap" |
| Create/refactor AGENTS.md | agents-md | "set up AGENTS.md", "create AGENTS.md", "refactor AGENTS.md" |
| Install regression-aware quality gates | quality-gates | "set up quality gates", "block new complexity", "baseline our tech debt", "stop agents adding dead code", "regression gate" |
| Check existing artifacts | audit | "audit docs", "are my docs up to date", "check agent readiness" |
If intent is ambiguous, ask the user which mode they want.
Startup: Recommend Project Skills
After selecting a mode and before making project changes, read references/recommended-skills.md and inspect the repository for its documented framework signals.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/agent-ready-template.md 5.7 KB
- assets/architecture-md-template.md 3.4 KB
- assets/docs-structure-template.md 3.6 KB
- assets/domain-knowledge-template.md 4.3 KB
- assets/quality-gate-ci-template.yml 1.5 KB
- assets/quality-gate-test-template.sh 3.8 KB runs code
- assets/quality-gate.py 22 KB runs code
- assets/quality-gates-guide-template.md 2.4 KB
- references/architecture-guide.md 4.2 KB
- references/progressive-disclosure.md 4.8 KB
- references/quality-gates-pattern.md 12 KB
- references/recommended-skills.md 7.7 KB
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 · 713 lines · 100 tokens per session scan A b2765f91924f
agent-ready is a skill published in the GitHub repository dgalarza/claude-code-workflows (59 stars, last pushed 5d ago), licensed MIT. It adds 100 tokens to every session and 8,843 once invoked, about $0.0005 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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.