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 agentmods add skills/tomzx/agents/create-goalsnpx skills add tomzx/agents --skill create-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/create-goals)<a href="https://agentmods.dev/skills/tomzx/agents/create-goals"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-goals.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01229 |
| Opus 5 | $0.00012 | $0.00615 |
| Sonnet 5 | $0.00005 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
create-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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Goals
Defines the project's objectives, key results, and ongoing KPIs as a single context-level artifact.
Other skills, especially create-needs-assessment, check proposed features against these goals for strategic alignment.
Without stated goals, prioritization is ad hoc: every feature feels equally important, and there is no way to tell whether a need advances the project or is tangential.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. .sdlc/context/project-overview.md(must exist, for purpose, scope, and stakeholders)..sdlc/context/goals.md(optional; if present, revise rather than replace, per Revision Mode below).- Existing features under
.sdlc/features/(optional, to backfill the alignment table).
Steps
- Read
.sdlc/context/project-overview.mdfor purpose, scope, and stakeholders. - Confirm the time horizon and period type (quarter, half, year) with the user if not already stated.
- For each objective, write a qualitative statement of what the project wants to achieve this period.
- Under each objective, define two to five key results: measurable targets with a clear measurement method.
- Distinguish key results (time-bound, period-scoped targets) from KPIs (ongoing indicators the project watches continuously).
- Name an owner for each objective.
- List explicit non-goals to prevent scope creep.
- Populate the alignment table: map existing features and planned initiatives to the objective they advance.
- Write the output to
.sdlc/context/goals.md. If it already exists, revise per Revision Mode.
Output Format
Use the template at skills/sdlc/templates/context/goals.md. Write the result to .sdlc/context/goals.md.
Revision Mode
If .sdlc/context/review-goals.md exists with verdict: changes-requested, revise the existing .sdlc/context/goals.md to address each finding rather than regenerating from scratch.
Preserve content the review did not challenge.
Goal Design Guidance
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.
- 3d ago First seen · 95 lines · 23 tokens per session scan A d12f52bde296
create-goals is a skill published in the GitHub repository tomzx/agents (5 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,229 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-08-31.
Other skills, from other repositories
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
requirements-author
Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts.
mps-aspect-actions
Use when defining or editing MPS node factories (the "actions" aspect) — NodeFactories roots, per-concept NodeFactory setup functions that initialize a freshly created node and optionally copy data from a replaced sampleNode, plus the actions aspect's CopyPasteHandlers and PasteWrappers roots. Reach for this skill…
mps-aspect-intentions
Use when defining or editing MPS intentions (the Alt+Enter context-action aspect) — adding IntentionDeclaration roots, parameterized or surround-with variants, description/isApplicable/execute blocks, child-filter functions, factory-initialized AST splicing, or debugging why an intention is not offered. Lives in the…
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
api-design
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.