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 commands/vikramgorla/mcp-swiss/speckit.tasksgit 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.tasks)<a href="https://agentmods.dev/commands/vikramgorla/mcp-swiss/speckit.tasks"><img src="https://agentmods.dev/badge/commands/vikramgorla/mcp-swiss/speckit.tasks.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.00565 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
speckit.tasks 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 6d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Speckit Command: /tasks
Command: /tasks <spec-id>
Purpose: Generate a complete implementation task checklist from a plan. Reads specs/<NNN>-*/plan.md and creates tasks.md.
Instructions for AI
When the user runs /tasks <spec-id>, read both the spec and plan in specs/0<spec-id>-*/ and generate a tasks.md with a complete checklist of implementation and test tasks.
Tasks Template
# Tasks: <Feature Name>
**Spec:** <NNN>
**Status:** Not Started | In Progress | Complete ✅
---
## Implementation Tasks
- [ ] Create `src/modules/<name>.ts`
- [ ] Define `<name>Tools` array with <N> MCP tool definitions
- [ ] Implement `handle<Name>(name, args)` switch
- [ ] `<tool_1>` — <method> <endpoint> with <params>
- [ ] `<tool_2>` — <method> <endpoint> with <params>
- [ ] Register module in `src/index.ts`
- [ ] Export tools list from module
## Test Tasks
- [ ] Unit tests: `tests/unit/<name>.test.ts`
- [ ] Tool definitions schema validation (required fields present)
- [ ] Parameter validation (required params)
- [ ] URL/body construction tests (mocked fetch)
- [ ] Error handling (404, empty response)
- [ ] Integration tests: `tests/integration/<name>.integration.ts`
- [ ] Live API call: `<tool_1>` with realistic params
- [ ] Live API call: `<tool_2>` with realistic params
- [ ] Edge case: not-found returns empty, not error
## Documentation Tasks
- [ ] README section with tool table
- [ ] Tool descriptions in source (inputSchema.description fields)
- [ ] docs/tool-specs.md section
- [ ] docs/tools.schema.json entries
- [ ] spec.md Known Limitations section updated after implementation
Rules
- Every tool in the spec gets its own implementation task line
- Unit tests MUST mock external HTTP (no live calls in unit tests)
- Integration tests use live APIs — document any known flaky tests
- Documentation tasks are not optional — README + tool-specs.md must be updated
- Mark tasks complete
[x]only after verifying they actually work - Add any discovered tasks that weren't in the original list — keep it current
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.
- 6d ago First seen · 69 lines · 0 tokens per session scan A e05327a6a263
speckit.tasks is a command published in the GitHub repository vikramgorla/mcp-swiss (22 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.