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 define-visiongit 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/define-vision)<a href="https://agentmods.dev/skills/tomzx/agents/define-vision"><img src="https://agentmods.dev/badge/skills/tomzx/agents/define-vision/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/define-vision"><img src="https://agentmods.dev/badge/skills/tomzx/agents/define-vision.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.00034 | $0.00467 |
| Opus 5.5 | $0.00014 | $0.00187 |
| Sonnet 5.5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
define-vision 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 22d 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
Define Vision
Turns a validated opportunity into a product vision and positioning statement. This skill writes the product-level anchor consumed by every downstream phase: who it is for, what change it creates, and why it wins.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - A validated opportunity (Validate gate
proceed):opportunity-tree.mdandexperiment-result.md.
Steps
- State the target customer precisely (the ICP, not "everyone").
Reference segments from
market.md. - Articulate the vision: the future where the customer's problem is solved. One sentence a stranger could repeat.
- Write the positioning statement: For [target], who [struggle], our product is [category] that [key benefit].
Unlike [alternative], we [differentiation]. Tie differentiation to gaps from
competitors.md. - Define what winning looks like in 12 months — the target state, not a feature list.
- State explicit non-goals: who and what is out of scope, to prevent vision creep.
- Write the result to
.pdlc/context/vision.md(the product-level anchor) and leave a pointer in the initiative directory noting which initiative established it.
Output Format
Use the template at skills/pdlc/templates/context/vision.md.
Because vision is product-level, it lives under .pdlc/context/, not the initiative directory.
If multiple initiatives coexist, merge rather than overwrite, and note conflicts.
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted.
Completion Checklist
- Target customer is specific (an ICP, not "all users")
- Vision is one repeatable sentence
- Positioning names a concrete alternative and a concrete differentiation
- Non-goals stated
Next Step
Load set-goals to translate the vision into measurable objectives and guardrails.
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.
- 22d ago Changed · +6 lines 4fbf119fed63
- 24d ago Changed 99b3e3183c35
- 1mo ago First seen · 43 lines · 34 tokens per session scan A dc187cfdcdbb
define-vision is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 467 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.