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 instructions/dgalarza/claude-code-workflows/claude-mdgit 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.00860 | $0.00860 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
claude-code-workflows CLAUDE.md 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Workflows
A plugin marketplace for Claude Code — skills, agents, and bundles that extend Claude's capabilities with specialized workflows.
For architecture details, design decisions, and the reasoning behind the plugin structure, see ARCHITECTURE.md.
Repository Structure
plugins/ # Each subdirectory is a standalone plugin
<plugin-name>/
.claude-plugin/plugin.json # Name, version, description, author
README.md # User-facing documentation
skills/<skill-name>/
SKILL.md # Frontmatter + instructions (required)
scripts/ # Executable code (optional)
references/ # Docs loaded into context as needed (optional)
assets/ # Templates, files used in output (optional)
.claude-plugin/marketplace.json # Registry of all available plugins
.agents/skills/ # Locally installed skills (e.g., skill-creator)
configs/ # Claude Code configuration guides
tips/ # Short-form workflow guides
scripts/ # Utility scripts
Key Conventions
- Plugin versions live in two places — bump both
plugins/<name>/.claude-plugin/plugin.jsonAND.claude-plugin/marketplace.json - SKILL.md frontmatter requires
name(kebab-case, max 64 chars) anddescription(max 1024 chars, no angle brackets) - Skill instructions use imperative/infinitive form, not second person
- All JSON files must be valid — CI checks this automatically
- Commit messages follow conventional commits:
feat:,fix:,chore:,docs:
Development Workflow
- Create or modify plugins under
plugins/ - Validate locally:
python3 .agents/skills/skill-creator/scripts/quick_validate.py plugins/<name>/skills/<skill-name> - CI validates skills and JSON on PRs automatically
- Bump version in both plugin.json and marketplace.json before merging
Releasing
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 · 78 lines · 860 tokens per session scan A 899d0ff7075b
claude-code-workflows CLAUDE.md is an instructions file published in the GitHub repository dgalarza/claude-code-workflows (59 stars, last pushed 5d ago), licensed MIT. It adds 860 tokens to every session, about $0.0043 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.