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 fall-out-bug/sdp --skill visiongit clone --depth 1 https://github.com/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/vision)<a href="https://agentmods.dev/skills/fall-out-bug/sdp/vision"><img src="https://agentmods.dev/badge/skills/fall-out-bug/sdp/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/fall-out-bug/sdp/vision"><img src="https://agentmods.dev/badge/skills/fall-out-bug/sdp/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.00016 | $0.00787 |
| Opus 5.5 | $0.00006 | $0.00315 |
| Sonnet 5.5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@vision
Transform project ideas into vision, PRD, and roadmap.
Workflow
- Interview (3-5 questions) — Problem, users, success, MVP, competitors
- 7 Expert Analysis — Product, Market, Technical, UX, Business, Growth, Risk. Output format (per expert):
## {Expert}\n**Summary:** 2-3 sentences.\n**Key finding:** One actionable insight.\n**Risk/opportunity:** If any.Avoid vague essays; be concrete. - Generate artifacts — PRODUCT_VISION.md, docs/prd/PRD.md (or docs/PROJECT_MAP.md), docs/roadmap/ROADMAP.md
- Extract features — docs/drafts/feature-{slug}.md for P0/P1
Write Plan (F101)
Before modifying any file, emit a write plan covering PRODUCT_VISION.md, PRD.md, ROADMAP.md, and feature drafts:
- Enumerate — List every file the skill will CREATE / MODIFY / DELETE with a one-line reason. Covers PRODUCT_VISION.md, PRD.md, ROADMAP.md, and feature drafts.
- Flags:
--dry-run— Emit write plan only. Do NOT create, modify, or delete any file.--yes— Skip confirmation prompt. Execute immediately. Intended for CI/non-interactive.
- Confirm — Present the plan to the user and wait for explicit approval (unless
--yes). - Log — Append write plan event to
.sdp/log/events.jsonl(sanitize file paths before logging: strip newlines, ensure valid JSON escaping):
Include context fields only when the ID is known at plan time. Omit unavailable fields rather than inventing placeholders.{"spec_version":"v1.0","event_id":"<uuid>","timestamp":"<ISO-8601>","source":{"system":"sdp-lab","component":"vision"},"event_type":"decision.made","payload":{"decision_type":"write_plan","plan":[{"path":"...","action":"CREATE|MODIFY|DELETE","reason":"..."}]},"context":{"feature_id":"<F-id if known>","workstream_id":"<ws-id if applicable>"}}Note: Phase 1 uses prompt-level write boundaries (CLI out of scope). Aligns with
sdp/schema/contracts/orchestration-event.schema.jsonviaevent_type: "decision.made". Phase 2 CLI will emit natively.
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 First seen · 64 lines · 16 tokens per session scan A 44c916af6854
vision is a skill published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 787 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
create-project
Scaffold a new project with git, .gitignore, CLAUDE.md, AGENTS.md, GitHub repo, and memory directory. Use when user says "start a new project", "create a repo", or "scaffold an app". Creates the project as a sibling to the .claude/ config directory.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
feedback-page-generator
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
status-page-generator
Deprecated compatibility entry for Status Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Status Page.
document-actions
Extract cited facts, obligations, deadlines and proposed actions from documents, preserving OCR uncertainty and reconciling Prismer tasks.