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/erionrb/agent-sdd-kitWrote 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/erionrb/agent-sdd-kit/project)<a href="https://agentmods.dev/rules/erionrb/agent-sdd-kit/project"><img src="https://agentmods.dev/badge/rules/erionrb/agent-sdd-kit/project/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/erionrb/agent-sdd-kit/project"><img src="https://agentmods.dev/badge/rules/erionrb/agent-sdd-kit/project.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.00732 | $0.00732 |
| Opus 5.5 | $0.00293 | $0.00293 |
| Sonnet 5.5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
project 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-sdd-kit
This is agent-sdd-kit — an open source SDD AI workflow toolkit and canonical setup provider for applying the SDD methodology to real software repositories. It is not a product codebase; it is the tooling, training, prompt, and setup layer reused across projects.
Workflow
All development in this repo follows the SDD cycle via OpenSpec CLI (v1.3.1):
Idea → proposal.md (what/why) → specs.md → design.md (how) → tasks.md (steps) → implement → review → QA
Key commands
| Command | What it does |
|---|---|
/opsx-propose |
Propose a new change — create it and generate all artifacts in one step |
/opsx-apply |
Implement tasks from an existing change |
/opsx-explore |
Explore / think through a problem before proposing |
/opsx-archive |
Archive a completed change into main specs |
CLI equivalents:
openspec new change <name> # scaffold a new change
openspec status --change <name> # check artifact completion
openspec list # list all active changes
openspec instructions apply --change <name> --json # get implementation instructions
Changes live in openspec/changes/<name>/ with .openspec.yaml and artifact files (proposal.md, specs.md, design.md, tasks.md).
The active schema is spec-driven: proposal → specs → design → tasks. Config is at openspec/config.yaml.
Structure
.claude/skills/ OpenSpec skills for Claude Code (opsx: propose, apply, explore, archive)
.cursor/rules/ Project context for Cursor (this file)
.cursor/commands/ OpenSpec slash commands for Cursor (opsx-propose, apply, explore, archive)
docs/training/path/ 8-step SDD learning path (start at README.md)
openspec/ OpenSpec project root (config + future changes/)
memory/ Persistent memory for agent sessions
What's missing (build these next)
The framework is partially set up. The docs/training/path/08-whats-next.md file has the full action checklist. Short version:
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 · 70 lines · 732 tokens per session scan A 5e49804aee87
project is a cursor rule published in the GitHub repository erionrb/agent-sdd-kit (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 732 tokens to every session, about $0.0029 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).