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 skills add shinpr/codex-workflows --skill recipe-fullstack-buildgit clone --depth 1 https://github.com/shinpr/codex-workflowsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/shinpr/codex-workflows/recipe-fullstack-build)<a href="https://agentmods.dev/skills/shinpr/codex-workflows/recipe-fullstack-build"><img src="https://agentmods.dev/badge/skills/shinpr/codex-workflows/recipe-fullstack-build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/shinpr/codex-workflows/recipe-fullstack-build"><img src="https://agentmods.dev/badge/skills/shinpr/codex-workflows/recipe-fullstack-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.01022 |
| Opus 5.5 | $0.00012 | $0.00409 |
| Sonnet 5.5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
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 16d 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 — 83 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
Invocation rule: Start each named agent with spawn_agent and fork_turns="none". When invoking the same named agent again within this flow, use followup_task on its existing instance with the inputs specified for the current invocation. Supply 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 Authorization.
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 Authorization. When user authorization to implement is absent from both the conversation and plan, 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 the user's instruction and scope in Implementation Authorization 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.
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.
- 16d ago Changed 084c8e579d49
- 17d ago Changed 5121e26997ac
- 1mo ago Changed · +2 lines 20c3ff98b088
- 1mo 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 (39 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,022 once invoked, about $0.0001 per session on Opus 5.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
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
agent-phase-closeout
A Chinese-language process for closing out a completed work stage and recording its state. It summarizes finished work, preserves decisions, freezes completed interfaces, and writes a resume checkpoint.
blueprint
Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation…
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.