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/sandeepshekhar26/develop-anythingWrote 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/sandeepshekhar26/develop-anything/auk-rules)<a href="https://agentmods.dev/rules/sandeepshekhar26/develop-anything/auk-rules"><img src="https://agentmods.dev/badge/rules/sandeepshekhar26/develop-anything/auk-rules/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/sandeepshekhar26/develop-anything/auk-rules"><img src="https://agentmods.dev/badge/rules/sandeepshekhar26/develop-anything/auk-rules.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.01103 | $0.01103 |
| Opus 5.5 | $0.00441 | $0.00441 |
| Sonnet 5.5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
auk-rules 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 2mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated by auk — AI Context Engineering Platform
https://github.com/sandeepshekhar26/develop-anything
Generated: 2026-06-11T17:08:30.055Z
Context Health: 100%
DO NOT EDIT MANUALLY — regenerate with: auk compile
🔴 architecture-no-utility-to-model: Utility layer should not import from Model layer. 1 existing violation is known tech debt — don't add more.
🔴 naming-functions-camelcase: All function names use camelCase naming convention.
🔴 naming-classes-pascalcase: All class and interface names use PascalCase naming convention.
🔴 testing-naming-test: Test files follow the *.test.ts / *.test.js naming convention.
🟡 architecture-hotspot-tests-helpers-expect-ts-expect: expect (tests/helpers/expect.ts) is called from 105 places — changes here have a high blast radius. Keep its signature and behavior stable.
🟡 architecture-hotspot-src-utils-logger-ts-info: info (src/utils/logger.ts) is called from 22 places — changes here have a high blast radius. Keep its signature and behavior stable.
🟡 architecture-hotspot-src-utils-logger-ts-success: success (src/utils/logger.ts) is called from 21 places — changes here have a high blast radius. Keep its signature and behavior stable.
🟡 architecture-god-class-src-utils-cli-ts-Command: Command (src/utils/cli.ts) has 18 methods and 24 inbound calls — it is becoming a god object. Don't add more responsibilities; split it instead.
🟡 architecture-god-class-tests-helpers-expect-ts-Expectation: Expectation (tests/helpers/expect.ts) has 15 methods and 2 inbound calls — it is becoming a god object. Don't add more responsibilities; split it instead.
🟡 architecture-hub-src-types-rules-ts: src/types/rules.ts has 32 connections — it may be becoming a god object. Consider breaking it into smaller modules.
🟡 architecture-hub-src-utils-logger-ts: src/utils/logger.ts has 31 connections — it may be becoming a god object. Consider breaking it into smaller modules.
🟡 architecture-hub-src-types-analysis-ts: src/types/analysis.ts has 30 connections — it may be becoming a god object. Consider breaking it into smaller modules.
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.
- 2mo ago First seen · 60 lines · 1,103 tokens per session scan A a16d2b2b5d59
auk-rules is a cursor rule published in the GitHub repository sandeepshekhar26/develop-anything (18 stars, last pushed 4mo ago), licensed MIT. It adds 1,103 tokens to every session, about $0.0044 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-30.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Search dreamd at the start of a task and quote a hit. Append when the user corrects you or states a decision.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.