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 adamlinscott/claude-skills --skill goal-workflowgit clone --depth 1 https://github.com/adamlinscott/claude-skillsWrote 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/adamlinscott/claude-skills/goal-workflow)<a href="https://agentmods.dev/skills/adamlinscott/claude-skills/goal-workflow"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/goal-workflow/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/adamlinscott/claude-skills/goal-workflow"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/goal-workflow.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.00236 | $0.02341 |
| Opus 5 | $0.00118 | $0.01171 |
| Sonnet 5 | $0.00047 | $0.00468 |
| Haiku 4.5 | $0.00024 | $0.00234 |
Grade A, and why
goal-workflow 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 9d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal Workflow
Turn a settled goal into a bounded implementation loop, then force proof, then fix or
close. This is the implementation-phase sibling to assumption-inventory (before),
reground (mid-drift), and fresh-eyes (after).
The orchestration engine is explicit subagent fan-out via the Agent tool — the only
multi-agent mechanism a skill can reliably drive. Native /goal and ultracode's automatic
workflow orchestration are user-only and discretionary (a skill cannot set /goal, and
ultracode decides for itself whether to author a workflow), so this skill does not depend on
them — it offers them as an optional fast path the user can run. /fresh-eyes is the
independent verifier. The skill's own job is to lock the goal, front-load decisions, map
terrain, and — the load-bearing step — write a checkable contract before any code, so
verification anchors to a bar set in writing, not to the implementer's memory of intent.
Run the steps in order. Step 0 is a hard gate; do not skip it.
0. Confirmation gate (FIRST — before anything else)
This skill runs a long, expensive, autonomous loop, and it depends on two session settings
a skill cannot set or detect for itself: ultracode effort (xhigh + workflow
orchestration) and auto-accept mode (so the loop's agents run without a permission
prompt on every action). Passing the keyword ultracode as an argument does not turn
effort on — only the user can, manually. So gate on an explicit --confirm flag that
asserts the user has done the setup.
- Inspect this invocation's
ARGUMENTSfor two flags:--confirm— required to run. Asserts the setup below is done.--commit— optional, default OFF. Governs all commit/push behavior for the run. Present → the skill commits at logical intervals and pushes at milestones. Absent → the skill makes no commits or pushes; version control stays entirely with the user.
--confirmpresent → setup confirmed. Record whether--commitis also present (it governs steps 5 and 8), then proceed to step 1.--confirmabsent → STOP. Modify nothing, then output the gate message and wait. Keep it to three sections in this order — goal, setup, start — and nothing more; brevity is the point. The full template is in REFERENCE.md; in short:- Goal — one line: the goal you'd lock (derived per step 1) and its source doc, so the user sees what they're committing to before the how.
- Set up —
/effort ultracodeand Shift+Tab → auto-accept. The skill can set neither; the user must do both. - Start it — A: re-invoke
/goal-workflow --confirm(skill-managed); or B: paste the generated/goal …command (user-run, fullest native fan-out). Close with a single footer line: autonomous, slow (~1 hr for large goals), token-heavy, and the git posture for this run (commit at intervals if--commit, else git stays with the user).
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.
- 9d ago First seen · 150 lines · 236 tokens per session scan A 752a42f98cf7
goal-workflow is a skill published in the GitHub repository adamlinscott/claude-skills (3 stars, last pushed 9d ago), licensed MIT. It adds 236 tokens to every session and 2,341 once invoked, about $0.0012 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-31.
Other skills, from other repositories
implement
Use in the Implement phase whenever writing or editing production Java code, or fixing a bug, in a Spring/Spring Boot project. Enforces test-first (red-green-refactor), executes the approved plan step by step, and honors the project's path-scoped tech-stack rules and the task's enforcement set. Preloaded into…
review
Use in the Review phase before claiming any Java/Spring task is complete, fixed, or passing. Spawns the auditor subagents that check the implementation against every applicable skill, rule, and memory item, runs the test suite for fresh evidence, and re-spawns for at most two fix rounds before reporting what survives.…
claudehut-workflow
Use at the start of every session and whenever beginning a coding task in a Java/Spring backend - establishes the ClaudeHut 7-phase agentic workflow, the complexity-tier routing that lets small tasks skip deliberation phases, and the laws that govern which skills and rules must fire. Injected at session start; also…
discover
Use as the FIRST phase of EVERY coding task, before brainstorming - grounds the work in the existing codebase (entry points, key types, structure) and proves whether something reusable already exists. Produces the reuse-scan artifact the write gate requires and the reuse DECISION (adopt / extend / new). Runs inline on…
write-plan
Use in the Plan phase after the spec is approved - dispatches the planner agent to draft the executable plan from the standard template (decision summary, T-xxx task breakdown with test-first + verify per task), gets the user's approval, records the plan (opening the write gate), and mirrors the breakdown into Claude…
brainstorm
Use to generate and weigh solution approaches for a problem, after discovery has grounded the context. Produces two or more genuinely distinct options scored on trade-offs, recommends one, and (for code tasks) assembles the enforcement set the rest of the workflow audits against. General-purpose ideation — works for…