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/onehillai/asdd/cursor-asddgit clone --depth 1 https://github.com/OneHillAI/ASDDWhat 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.00190 | $0.00190 |
| Opus 5 | $0.00095 | $0.00095 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
cursor-asdd 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
This repository is governed by ASDD (Agentic Spec-Driven Development). Read AGENTS.md, the contribution constitution, before writing code here. These points are a pointer to it, not a second set of rules.
- Disclose the agent in the pull request and the commit trailer, and sign every commit off (
git commit -s). - Exactly one lane label per pull request; the set is in
.asdd.yml. - A feature or fix points to a spec that defines "done"; only the
chorelane is spec-exempt. - You are the developer. The test agents run on a different model, so your own tests are not the deciding check.
- A human merges. Agents review and recommend; you do not merge your own work.
Full guide: docs/guides/bring-your-own-developer.md
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 · 16 lines · 190 tokens per session scan A 2f36694c9314
cursor-asdd is a cursor rule published in the GitHub repository OneHillAI/ASDD (5 stars, last pushed 21d ago), licensed Apache-2.0. It adds 190 tokens to every session, about $0.0010 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
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
minimax-mcp-tools
MCP and web-tool guidance: current-doc retrieval, direct-tool preference, MCP Apps structured content, and version-aware external lookups.
repo-context
Read AGENTS.md first. Treat it as the source of truth for this repo's commands, invariants, public naming, release constraints, and first-user path.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.