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 autohandai/code-cli --skill goal-writergit clone --depth 1 https://github.com/autohandai/code-cliWrote 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/autohandai/code-cli/goal-writer)<a href="https://agentmods.dev/skills/autohandai/code-cli/goal-writer"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/goal-writer/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/autohandai/code-cli/goal-writer"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/goal-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01259 |
| Opus 5.5 | $0.00022 | $0.00504 |
| Sonnet 5.5 | $0.00011 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
goal-writer 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a good goal
Help the user turn a rough intention into one or more /goal objectives that
goal mode can pursue across many turns without supervision. A goal is not a task
description; it is a completion contract. It says what must become true, how
that truth is proven, where the work may and may not reach, and when to stop and
report.
Drafting and starting are separate steps. Settle the wording first. Only once
the user has approved the exact objective should you call create_goal. When
the user approves more than one objective, call create_goal for each approved
goal in the intended order; the first starts and the rest are queued.
Ask, do not narrate choices
When a decision has concrete options, use the host's user-question tool if it is available. Do not write a prose menu and ask the user to answer in free text.
Examples of choices that should use the tool:
- narrow vs broad scope
- which proof command to use
- whether to include a budget
- which budget size
- which permission mode or execution mode to use
If no user-question tool is available, fall back to a short plain-text question with clearly labeled options and wait. Open-ended questions are fine in prose.
Rules
- Only help when the user asks for goal-writing help. Do not wrap ordinary work in goal mode on your own.
- Write the draft in the user's language.
- Always show the full drafted objective before starting it.
- Get explicit approval before calling
create_goal. - Draft with the user. Offer a draft, explain the choices, invite changes, and revise.
- If the user wants a looser goal after you point out the trade-off, write their version. Do not keep relitigating it.
- Do not set a token budget unless the user asks or the work is clearly open-ended enough that a budget is useful.
- Never bake a turn cap into the objective text.
What makes a goal good
Strong goals define proof, not effort.
Include as many of these as the task warrants:
- End state: the concrete condition that must become true.
- Proof: observable evidence, preferably a command, test, search, file, or metric.
- Boundaries: what may be touched and what is off limits.
- Loop: how to iterate, such as rerunning a check after each change.
- Stop rule: when to stop and report instead of forcing a pass.
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.
- 1mo ago Changed · +6 lines 4093b7e92180
- 1mo ago First seen · 125 lines · 56 tokens per session scan A eb2250a04d77
goal-writer is a skill published in the GitHub repository autohandai/code-cli (210 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,259 once invoked, about $0.0002 per session on Opus 5.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
neuron-laravel-integration
Integrate Neuron AI agents into a Laravel 13 app the framework-native way — setup checklist (App\Neuron layout, config/services.php keys, one migration, NeuronServiceProvider, bootstrap/app.php exception mapping, neuron:evaluate), container-built agents bound per thread with for(), thread authorization, JSON and…
neuron-evaluation
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
neuron-agent
Create, configure, and extend Neuron AI agents in PHP using providers, tools, chat history, memory, and custom workflow nodes. Use for Neuron Agent implementation, configuration, conversation lifecycle, and input/output extensions.
neuron-rag
Implement RAG (Retrieval-Augmented Generation) with Neuron AI including vector stores, embeddings providers, document loaders, retrieval strategies, and metadata filtering. Use this skill whenever the user mentions RAG, retrieval, vector search, document retrieval, semantic search, knowledge bases, chat with…
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…
neuron-tool-approval
Implement human-in-the-loop tool approval flows with Neuron AI agents — gating risky tools behind approve/deny decisions, rendering approval UIs from chat history, submitting decisions, and building a single endpoint that handles both conversation turns and approval continuations. Use this skill whenever the user…