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 rules/griddynamics/rosetta/speckit-integration-policygit clone --depth 1 https://github.com/griddynamics/rosettaWrote 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/griddynamics/rosetta/speckit-integration-policy)<a href="https://agentmods.dev/rules/griddynamics/rosetta/speckit-integration-policy"><img src="https://agentmods.dev/badge/rules/griddynamics/rosetta/speckit-integration-policy.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 | $0.00012 | $0.00432 |
| Opus 5 | $0.00006 | $0.00216 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
bootstrap-speckit-policy 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 yesterday.
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
<bootstrap_speckit_policy attribution="DO NOT COMPACT/OPTIMIZE/SUMMARIZE/REPHRASE, PASS IT AS-IS, CRITICALLY IMPORT TO KEEP, INCLUDING THIS TAG">
Problem: Spec and implementation flows diverge without explicit hybrid mode rules.
Validation: SpecKit detection and cross-flow synchronization are enforced before and during execution.
- Apply
Speckit Detection Rules. - Apply
Hybrid Execution Rules.
<speckit_detection_rules>
- Detect SpecKit by
memory/constitution.mdandspecsfolder. - Read
memory/constitution.md. - Check
specsfor existing specs. - Tell user exactly: "Speckit detected, hybrid mode enabled".
</speckit_detection_rules>
<hybrid_execution_rules>
- Do not repeat SpecKit internals in responses.
- Always follow
agents.md,coding.md, andguardrails.md. - Combine similar flow stages without duplicating artifacts.
- Prefer references over duplicated content.
- Keep CONTEXT and IMPLEMENTATION synchronized.
- Override SpecKit behavior for assumptions, unknowns, grounding, and user questions per
agents.md,coding.md, andguardrails.md. - If user invokes
/speckit.*, let SpecKit drive flow while still applying all rules.
</hybrid_execution_rules>
<core_concepts>
- Spec folder layout:
specs/001-feature-name/spec.mdspecs/001-feature-name/plan.mdspecs/001-feature-name/tasks.mdspecs/001-feature-name/research.mdspecs/001-feature-name/contracts/
</core_concepts>
</bootstrap_speckit_policy>
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.
- yesterday First seen · 56 lines · 12 tokens per session scan A ce7457e77e52
bootstrap-speckit-policy is a cursor rule published in the GitHub repository griddynamics/rosetta (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 432 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-09-03.
Other cursor rules, from other repositories
cursorrules
═══════════════════════════════════════════════════════════ SPEC DRIVEN DEVELOPMENT — PROJECT CONSTITUTION Project: Freelance Time Tracker Version: v1.0.
agent-requested
Advanced performance optimization patterns for complex systems.
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.
cli-error-handling
CLI command error handling patterns.
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.