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 tomzx/agents --skill set-goalsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/set-goals)<a href="https://agentmods.dev/skills/tomzx/agents/set-goals"><img src="https://agentmods.dev/badge/skills/tomzx/agents/set-goals/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/tomzx/agents/set-goals"><img src="https://agentmods.dev/badge/skills/tomzx/agents/set-goals.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.00510 |
| Opus 5 | $0.00015 | $0.00255 |
| Sonnet 5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
set-goals 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 6d 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.
What it actually says
Set Goals
Translates the vision into measurable objectives, key results, and the two metric types that define success: success metrics (what must improve) and guardrail metrics (what must not regress). The classic PM failure is moving the measured metric while breaking three unmeasured ones; guardrails are the antidote and are mandatory here.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. vision.mdfromdefine-vision.
Steps
- Define 1-3 objectives (qualitative outcomes aligned to the vision).
- For each objective, define 2-4 key results that are measurable and time-bound.
- List success metrics (
SM-N): the numbers that must move for the initiative to count as a win. Each gets a baseline, a target, and a measurement source. - List guardrail metrics (
GM-N): the numbers that must hold (e.g., latency, churn, error rate, cost-per-unit). Each gets a current value and a floor it must not cross. If you cannot name a guardrail, that is a finding — it means you do not know what you could break. - Confirm every metric has an owner and a measurement source (instrumentation, report, manual). Metrics without a source are wishes.
- Write the result to
.pdlc/context/goals.md(product-level) and/or the initiative directory for initiative-specific goals.
Output Format
Use the template at skills/pdlc/templates/initiatives/goals.md (also used as the context template). Each metric row: ID, name, type (success/guardrail), baseline, target/floor, owner, source.
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted.
Completion Checklist
- At least one success metric and at least one guardrail metric
- Every metric has a baseline, target/floor, owner, and measurement source
- Key results are time-bound
- No metric is "we will improve X" without a number
Next Step
Load build-roadmap to sequence initiatives against these goals.
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.
- 6d ago First seen · 43 lines · 29 tokens per session scan A a3f3830bb5ca
set-goals is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 510 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…