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/vscarpenter/gsd-task-manager/qspecgit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWhat 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.00021 | $0.00315 |
| Opus 5 | $0.00010 | $0.00158 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
qspec 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 2d 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
Write a spec for the described feature. Follow the Spec-Driven Development standards in coding-standards.md Part 1 and the project conventions in CLAUDE.md.
Feature: $ARGUMENTS
Include every section:
- Goal — One sentence describing what this does and why it matters for gsd-taskmanager.
- Inputs / Outputs — Schemas (reference
lib/schema.tsZod types if applicable), data shapes, formats. - Constraints — Performance, privacy (local-first IndexedDB), PocketBase sync compatibility, file-size limits (≤350 lines per file, ≤30 lines per function), bundle impact.
- Edge Cases — Empty inputs, offline mode, sync conflicts, circular task dependencies, concurrent multi-device edits, schema migration scenarios.
- Out of Scope — Explicit list of what this version does NOT do (prevents scope creep).
- Acceptance Criteria — Checkable statements that prove correctness. Each AC must map to at least one test.
- Test Stubs — Empty test function signatures (vitest, behavior-based names like
should_persist_task_when_quadrant_changes) mapping to each acceptance criterion.
Save the spec to tasks/spec.md. If a spec already exists there, append a new section dated with today's date rather than overwriting.
Do not write any implementation code. Wait for spec approval before proceeding to /tdd.
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.
- 2d ago First seen · 21 lines · 21 tokens per session scan A 37fd83823626
qspec is a command published in the GitHub repository vscarpenter/gsd-task-manager (24 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 315 once invoked, about $0.0001 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-30.
Other commands, from other repositories
methodology
View your cognitive methodology profile and reasoning patterns.
release
Comprehensive workflow for releasing a new version of the VectorMCP Ruby gem following best practices.
compile
Compile a FIBER decision context (world + query) and report the oracle verdict, omission accounting, and certificate digest faithfully.
safety-check
Verify the EA1 safety gate blocks all destructive actions on a page.
2-spec
Command "2-spec" from clchinkc/document-mcp, covering requirements gathering generation, behavioral scenario generation (optional), design document creation generation and implementation planning generation.
git
Git operations with intelligent commit messages and workflow optimization.