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/baodq97/open-plugin/goal-definenpx skills add baodq97/open-plugin --skill goal-definegit clone --depth 1 https://github.com/baodq97/open-pluginWrote 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/baodq97/open-plugin/goal-define)<a href="https://agentmods.dev/skills/baodq97/open-plugin/goal-define"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/goal-define.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.00132 | $0.02047 |
| Opus 5 | $0.00066 | $0.01024 |
| Sonnet 5 | $0.00026 | $0.00409 |
| Haiku 4.5 | $0.00013 | $0.00205 |
Grade A, and why
goal-define 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal Define
Turn rough user input into a structured, verifiable /goal text through guided interview.
A well-structured goal has a control core — four sections that prevent the agent from wandering or over-committing:
| Section | Purpose |
|---|---|
| Constraints | Hard fences — what you CANNOT do |
| Operating rules | How you work — iteration size, scope control |
| Done when | Finish line — measurable success criteria |
| Pause if | Abort conditions — stop instead of grinding |
Without all four, autonomous work either wanders or burns tokens on doomed approaches.
Process
Work through these phases in order. Each phase fills one section of the goal template.
Use AskUserQuestion for structured choices. Ask one question per message.
Phase 1: Detect Task Type
Classify the user's intent into one of four types. This determines which optional sections to include and how to phrase interview questions.
| Type | Signal phrases | Extra sections |
|---|---|---|
| Implementation | "build", "fix", "add", "implement", "deploy" | Components to build, Storage layout |
| Exploration | "explore", "understand", "trace", "diagram", "how does X work" | Method (tools), Output format constraints |
| Audit | "review", "check", "audit", "validate", "security" | Areas to examine, Severity classification |
| Refactoring | "refactor", "restructure", "clean up", "migrate" | Before/after criteria, Regression checks |
If ambiguous, ask the user. If the user's input already makes the type obvious, skip this question.
Phase 2: Title & Scope
Extract or ask for:
- One-line title:
<Task Type>: <description in ≤ 10 words> - Scope boundary: What is explicitly IN scope? What is OUT?
If the user's initial input is detailed enough, propose a title and confirm.
Phase 3: Context Discovery
Identify what the agent should read before starting work.
Context-aware discovery: Check what's available in the current environment and suggest accordingly:
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.
- 3d ago First seen · 196 lines · 132 tokens per session scan A 08db685f7745
goal-define is a skill published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 132 tokens to every session and 2,047 once invoked, about $0.0007 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
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.