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 tt-a1i/matt-skills-with-to-goal --skill execute-spec-in-forkgit clone --depth 1 https://github.com/tt-a1i/matt-skills-with-to-goalWrote 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/tt-a1i/matt-skills-with-to-goal/execute-spec-in-fork)<a href="https://agentmods.dev/skills/tt-a1i/matt-skills-with-to-goal/execute-spec-in-fork"><img src="https://agentmods.dev/badge/skills/tt-a1i/matt-skills-with-to-goal/execute-spec-in-fork/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/tt-a1i/matt-skills-with-to-goal/execute-spec-in-fork"><img src="https://agentmods.dev/badge/skills/tt-a1i/matt-skills-with-to-goal/execute-spec-in-fork.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 45 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Memory Poisoning · line 85 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00117 | $0.01709 |
| Opus 5 | $0.00059 | $0.00855 |
| Sonnet 5 | $0.00023 | $0.00342 |
| Haiku 4.5 | $0.00012 | $0.00171 |
Grade A, and why
execute-spec-in-fork 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 12d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Spec in Fork
Turn one approved SPEC READY into a disposable Codex execution task. Keep product decisions in the planning task, keep implementation logs in the fork, and return evidence to the planning task automatically.
Require a launchable contract
Before creating anything:
- Find the latest completed
SPEC READYblock and apply later user corrections. - Require it to route to forked execution, fit one reliable implementation session, and contain no unresolved product decisions. Use
/to-ticketsor/to-goalwhen it does not. - Require the current harness to expose native Codex App task tools for forking, messaging, reading, naming, pinning, and archiving.
- Require
/codex-task-messengerto be installed with its Ask, Reply, and Resume card protocol (v2 or later) available.
If a prerequisite is missing, do not create a plain new task or simulate the transport. Explain the missing capability and give the manual fallback: fork from the final SPEC READY, run /spec-executor there, and paste its receipt back. After the receipt is pasted, ask once for Goal / spec quality; a skipped answer does not block using the receipt.
Harness capability map
This workflow is a Codex App adapter, so it depends on that harness's task tools by name. The names live here and nowhere else; everything below this section is written in capabilities. When a tool is renamed or reshaped, change this table only. The decision and its consequences live in ADR 0003.
| Capability | Codex App tool (harness-specific) |
|---|---|
| Fork the calling task into a same-directory child | fork_thread |
| Read a child task's current state | read_thread |
| Block until a child finishes — not used by default | wait_threads |
| Archive a validated child task | set_thread_archived |
| Identify the source task behind an inbound card | the App-supplied source_thread_id |
Titling and pinning use the App's native task controls and are referred to by what they do.
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.
- 12d ago First seen · 106 lines · 117 tokens per session scan A a03e50faea18
execute-spec-in-fork is a skill published in the GitHub repository tt-a1i/matt-skills-with-to-goal (160 stars, last pushed 15d ago), licensed MIT. It adds 117 tokens to every session and 1,709 once invoked, about $0.0006 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
projectatlas
Use ProjectAtlas as the atlas-first orientation layer before broad source reads, with MCP-first task startup, short-alias worktree registration and routing, safe targeted initialization, ranked navigation, exact or federated graph evidence, purpose curation, health, lint, and repository-wide token reporting.
codex-coding-plugin
Build, review, or fix ProjectAtlas plugin/runtime installer integration for Codex, Claude Code, and OpenCode, especially version convergence, stale ProjectAtlas cache repair, MCP config generation, skill artifacts, host smoke tests, and fake-host tests for ProjectAtlas releases.
breaking-down-the-work
Splits scope into a product-first work breakdown that follows the 100% rule, keeps pieces from overlapping, uses outline numbers, and gives every piece a dictionary entry. Use when an epic, feature, or new subsystem needs a clean split into deliverables, or one source of truth before folders or work begin. Do not use…
staying-on-mission
Tests the current work against a written, lasting mission anchor and forces one choice, re-anchor, escalate, or stop. Use when an agent keeps finishing tasks but the work drifts from the goal, scope creeps, the same action repeats in a loop, or standards slip one small step at a time. Do not use for a tiny edit with…
closing-stale-packets
Brings an abandoned or half-filled change packet to an honest terminal state by completing it, closing it with a recorded rationale, or deleting it. Use when ng status flags a scaffold or invalid packet, a long session left a draft behind, or work was abandoned mid-packet. Do not use for an actively in-progress…
learning-from-experience
Turns incidents, near misses, bad handoffs, review surprises, escaped bugs, and signals from real use into lasting fixes to your safeguards. Use after something went wrong or nearly did and a future safeguard should change. Do not use during a live incident, which comes first, or to blame someone.