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/codex-workflows/recipe-fullstack-buildnpx skills add shinpr/codex-workflows --skill recipe-fullstack-buildgit clone --depth 1 https://github.com/shinpr/codex-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.00029 | $0.00943 |
| Opus 5 | $0.00015 | $0.00472 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
recipe-fullstack-build 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.
This is a copy
86% identical to recipe-build — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Required Skills [LOAD BEFORE EXECUTION]
coding-rulestestingai-development-guidesubagents-orchestration-guidellm-friendly-context
Every spawn_agent call uses fork_turns="none" and supplies exact artifact paths.
Orchestrator Role
The orchestrator owns plan selection, approval dialogue, task-set computation, filename routing, commits, and completion reporting. Invoke specialist agents for task decomposition, implementation, test review, quality repair, and final verification. A user-requested plan revision follows Work Plan Approval.
Work plan: $ARGUMENTS
1. Resolve the Work Plan
Apply subagents-orchestration-guide Work Plan Resolution with the backend, frontend, and shared patterns from Step 4 as the managed task patterns, excluding basenames that start with integration-tests-.
Report a missing Work Plan as the exact missing prerequisite.
2. Approval Gate
Apply subagents-orchestration-guide Work Plan Approval. When plan-level user approval is absent or ambiguous, ask before agent invocation or task analysis:
Approve this Work Plan as the implementation scope and authorize task decomposition, implementation, quality fixes, and per-task commits?
[path]
Record approval in the plan's existing plan-level status field and proceed to Step 3. A requested change returns through work-planner and document review before this gate.
3. Conditional Environment Preparation
Proceed directly to task generation. Run recipe-prepare-implementation only when the user explicitly requests repository-local setup. If task-local execution later identifies a concrete missing repository capability, resolve it through Orchestrator Escalation Resolution and run the preparation side path when that is the smallest authorized resolution.
4. Compute the Consumed Task Set
Use only:
docs/plans/tasks/{plan-name}-backend-task-*.mddocs/plans/tasks/{plan-name}-frontend-task-*.mddocs/plans/tasks/{plan-name}-task-*.mdfor shared or non-layered tasks
What ships with it
1 file 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.
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 · 81 lines · 29 tokens per session scan A 5b27b5b164e4
recipe-fullstack-build is a skill published in the GitHub repository shinpr/codex-workflows (38 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 943 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to recipe-build, differing in 42 lines, and is treated as a copy.
Other skills, from other repositories
chrome-cdp
Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
imsg
Use imsg to read and send iMessage/SMS via macOS Messages.app.
ax-python-agent
Use when writing Python code with axllm for agents, child delegation, tools, MCP, citations, persistent playbook learning, stage instructions, runtime state, final typed responses, and direct-respond executor skipping.
ax-cpp-agent-rlm
Use when writing C++ code with axllm for RLM executor loops, AxCodeRuntime sessions, runtime envelopes, process runtimes, and optional runtime profiles.