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/shinpr/claude-code-workflows/recipe-tasknpx skills add shinpr/claude-code-workflows --skill recipe-taskgit clone --depth 1 https://github.com/shinpr/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.00015 | $0.00535 |
| Opus 5 | $0.00008 | $0.00267 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
recipe-task 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explicit User Instruction: The user explicitly instructs and authorizes every subagent call named in this recipe. Execute each applicable call when its prerequisites are met.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before making workflow decisions, invoking agents, or resolving findings.
Task Execution with Metacognitive Analysis
Task: $ARGUMENTS
Mandatory Execution Process
Step 1: Rule Selection via rule-advisor (REQUIRED)
Invoke rule-advisor using Agent tool:
subagent_type: "dev-workflows-frontend:rule-advisor"description: "Rule selection"prompt: "Task: $ARGUMENTS. Select appropriate rules and perform metacognitive analysis."
Step 2: Utilize rule-advisor Output
After receiving rule-advisor's JSON response, proceed with:
-
Understand Task Essence (from
taskAnalysis.essence)- Focus on fundamental purpose, not surface-level work
- Distinguish between "quick fix" vs "proper solution"
-
Follow Selected Rules (from
selectedRules)- Execute each selected skill by its
skillname and read it completely - Apply the named sections in the context of the complete skill
- Execute each selected skill by its
-
Recognize Past Failures (from
metaCognitiveGuidance.pastFailures)- Apply countermeasures for known failure patterns
- Use suggested alternative approaches
-
Execute First Action (from
metaCognitiveGuidance.firstStep)- Start with recommended action
- Use suggested tools first
Step 3: Bind the Execution Sequence
Before implementation, derive the smallest dependency-ordered sequence required by the rule-advisor result. Its first gate applies and maps the selected rules; its final gate verifies those rules and the requested outcome. Execute one gate at a time, advancing only when its required evidence exists. Add or reorder a gate only when new evidence changes a dependency or completion condition.
Step 4: Execute Implementation
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 · 57 lines · 15 tokens per session scan A 3bba0872867e
recipe-task is a skill published in the GitHub repository shinpr/claude-code-workflows (675 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 535 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
dynamic-workflows
Ultracode / Max-Parallel mode — dynamic workflows fan work out across tens–hundreds of adversarially-verified parallel subagents for large, decomposable jobs (codebase-wide audits, big migrations, cross-checked research). Opt-in; higher token spend.
agent-teams
Experimental Agent Teams orchestration — run CCGodMode agents as parallel teammates with SharedTaskList coordination (requires CLAUDECODEEXPERIMENTALAGENTTEAMS=1).
cost-efficiency
Smart Routing — the DEFAULT CCGodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.
quality-gates
Parallel quality gate orchestration — @validator and @tester run simultaneously after @builder, with mandatory decision matrix for pass/fail routing.
sprint-planning
Plan-first orchestration (ADR-004): comprehensive PLAN.md, sprint files with write-scope ownership, preflight checks, serialized integration, and the release sprint. Use for any non-trivial or multi-part request BEFORE dispatching agents.
workflows
CCGodMode Full-Gates workflow definitions — used for high-risk work and when Smart Routing escalates. Default routing is Smart Routing (skills/cost-efficiency/).