Borrowing it
Nothing to install: this file belongs to vikramgorla/mcp-swiss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vikramgorla/mcp-swiss/main/.specify/commands/speckit.plan.mdgit clone --depth 1 https://github.com/vikramgorla/mcp-swissWrote 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/commands/vikramgorla/mcp-swiss/speckit.plan)<a href="https://agentmods.dev/commands/vikramgorla/mcp-swiss/speckit.plan"><img src="https://agentmods.dev/badge/commands/vikramgorla/mcp-swiss/speckit.plan.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.1 | $0.00000 | $0.00468 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
speckit.plan 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 7d 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
Speckit Command: /plan
Command: /plan <spec-id>
Purpose: Generate an architectural plan from a spec. Reads specs/<NNN>-*/spec.md and creates plan.md.
Instructions for AI
When the user runs /plan <spec-id> (e.g. /plan 005), read the corresponding specs/0<spec-id>-*/spec.md and generate a plan.md in the same directory.
Plan Template
# Plan: <Feature Name>
**Spec:** <NNN>
**Status:** Draft | In Progress | Implemented ✅
---
## Architectural Vision
<2-4 sentences describing the overall approach. What pattern is used? Why?>
## Data Flow
\```
<ASCII diagram showing the data flow from MCP tool call → implementation → API → response>
\```
## Key Design Decisions
1. **<decision title>:** <rationale>
2. **<decision title>:** <rationale>
## Module Structure
\```
src/modules/<name>.ts
├── <ToolName>Tools: array — MCP tool definitions
└── handle<Name>(name, args) — tool call dispatcher
\```
## Edge Cases
| Case | Handling |
|------|----------|
| <edge case> | <how handled> |
## Error Handling
| Scenario | HTTP Status | Handling |
|---------|-------------|----------|
| <scenario> | <status> | <handling> |
## Performance Notes
- <performance characteristic>
- <caching approach if any>
- <timeout considerations>
## Security & Privacy
- <note on data handling>
- <auth requirements if any>
Rules
- Plan must match the spec — every P0 tool in spec.md must be covered in the plan
- Data flow diagram must be ASCII art — no images
- Edge cases must include: not-found, API error, missing required params
- If using a new HTTP pattern (POST body, path params, etc), document it explicitly
- Flag any dependencies on other modules or external systems
- Note coordinate system quirks (WGS84 vs LV95 for geodata)
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.
- 7d ago First seen · 77 lines · 0 tokens per session scan A bee3aea618e9
speckit.plan is a command published in the GitHub repository vikramgorla/mcp-swiss (22 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 468 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.