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/symboliclight-agi/governspec/cursor_procurementgit clone --depth 1 https://github.com/SymbolicLight-AGI/GovernSpecWrote 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/symboliclight-agi/governspec/cursor_procurement)<a href="https://agentmods.dev/rules/symboliclight-agi/governspec/cursor_procurement"><img src="https://agentmods.dev/badge/rules/symboliclight-agi/governspec/cursor_procurement.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.00145 | $0.00145 |
| Opus 5 | $0.00072 | $0.00072 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
cursor_procurement 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 3d 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
Cursor Procurement Rules
Project Goal
Summarize vendor procurement risks and identify approval blockers.
Working Constraints
- Do not approve purchases.
- Do not contact vendors.
- Do not infer legal approval.
Allowed and Forbidden Operations
- Web access: forbidden
- Network access: forbidden
- Filesystem read: allowed
- Filesystem write: forbidden
Human Confirmation Rules
- Any purchase or vendor commitment is requested -> ask_confirmation
Output Expectations
- Format: markdown
- Language: en
- Section: Procurement Decision
- Section: Missing Inputs
- Section: Risk Notes
- Section: Manual Approval
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.
- 3d ago First seen · 36 lines · 145 tokens per session scan A 425e1e0b9c08
cursor_procurement is a cursor rule published in the GitHub repository SymbolicLight-AGI/GovernSpec (2 stars, last pushed 3mo ago), licensed MIT. It adds 145 tokens to every session, about $0.0007 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-31.
Other cursor rules, from other repositories
sigma-reports
Build, validate, retrieve, and safely update Sigma report code representations through /v2/reports/spec. Use for fixed-layout or pixel-perfect reports, invoices, statements, regulatory documents, and PDF delivery. Covers report pages, absolute pixel layout, header/footer panels, common elements, verification…
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
accessibility-guidelines
Accessibility guidelines for Angular + TypeScript applications to ensure inclusive design and compliance with WCAG standards.
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
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.