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.
git clone --depth 1 https://github.com/Project-VIC-International/Agentic-AI-Development-CourseWrote 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/rules/project-vic-international/agentic-ai-development-course/speckit-workflow)<a href="https://agentmods.dev/rules/project-vic-international/agentic-ai-development-course/speckit-workflow"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/speckit-workflow/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/rules/project-vic-international/agentic-ai-development-course/speckit-workflow"><img src="https://agentmods.dev/badge/rules/project-vic-international/agentic-ai-development-course/speckit-workflow.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.01462 | $0.01462 |
| Opus 5.5 | $0.00585 | $0.00585 |
| Sonnet 5.5 | $0.00292 | $0.00292 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
speckit-workflow 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 18d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development
Every feature, enhancement, and non-trivial bug fix in this project MUST follow the spec-driven development pipeline. Do not skip steps. Do not jump straight to implementation. The spec is the contract between you (the investigator), the AI agent, and any future developer, examiner, validator, or judge who needs to understand what the tool does and why.
This is the discipline that separates a court-defensible mission tool from a one-off script.
The Required Pipeline
| Step | Slash Command | What Happens |
|---|---|---|
| 1. Constitution | /speckit.constitution |
The project's governing rules (this is a one-time setup, then it lives at .specify/memory/constitution.md) |
| 2. Specify | /speckit.specify |
Define what the feature does, who uses it, what counts as "done" — in plain language |
| 3. Clarify | /speckit.clarify |
Answer the agent's questions about anything unclear before planning |
| 4. Plan | /speckit.plan |
Translate the spec into architecture, data models, components, and contracts |
| 5. Tasks | /speckit.tasks |
Break the plan into ordered, testable work units with clear acceptance criteria |
| 6. Analyze | /speckit.analyze |
Read-only cross-check of the spec, plan, and tasks before any code is written |
| 7. Implement | /speckit.implement |
Execute tasks one phase at a time; each phase is reviewed before moving on |
| 8. Converge | /speckit.converge |
Check the code against the spec, plan, and tasks; missed work is added to tasks.md and implemented |
GitHub spec-kit (https://github.com/github/spec-kit) provides these commands. They are not optional ritual — they are how a non-programmer keeps control of an AI agent that can write code faster than any human can read it.
The commands are shown in Spec Kit's reference spelling. Your agent may show them slightly differently (for example /speckit-specify in GitHub Copilot or $speckit-specify in Codex). Older Spec Kit versions do not have /speckit.converge; run /speckit.analyze again after implementation instead.
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.
- 18d ago Changed · +4 lines · +163 tokens per session 16df063f4213
- 2mo ago First seen · 88 lines · 1,299 tokens per session scan A c810c12f5ac2
speckit-workflow is a cursor rule published in the GitHub repository Project-VIC-International/Agentic-AI-Development-Course (5 stars, last pushed 14d ago), licensed Apache-2.0. It adds 1,462 tokens to every session, about $0.0058 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-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.