recipe-task

A workflow that chooses and applies the right project rules while completing a coding task. It uses a rule-selection step and additional guidance for preparing prompts, coordinating agents, and checking the work.

In plain words
What is it for?
Use it to run development tasks that require rule selection, metacognitive checks, generated prompts, handoffs, or multiple collaborating agents.
Why use it?
It helps an agent follow repository-specific instructions instead of treating every task the same way. It also makes decisions about task scope and agent coordination more deliberate.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/shinpr/claude-code-workflows/recipe-task
Any agent
npx skills add shinpr/claude-code-workflows --skill recipe-task
Clone the repo
git clone --depth 1 https://github.com/shinpr/claude-code-workflows

Made for: Claude Code, Codex.

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 535 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 3bba0872867e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

dev-workflows-frontend/skills/recipe-task/SKILL.md · 57 lines

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:

  1. Understand Task Essence (from taskAnalysis.essence)

    • Focus on fundamental purpose, not surface-level work
    • Distinguish between "quick fix" vs "proper solution"
  2. Follow Selected Rules (from selectedRules)

    • Execute each selected skill by its skill name and read it completely
    • Apply the named sections in the context of the complete skill
  3. Recognize Past Failures (from metaCognitiveGuidance.pastFailures)

    • Apply countermeasures for known failure patterns
    • Use suggested alternative approaches
  4. 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

Read the full file on GitHub · 57 lines

Changes

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.

  1. 2d ago First seen · 57 lines · 15 tokens per session scan A 3bba0872867e

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories