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/sruja-ai/sruja/sruja-devgit clone --depth 1 https://github.com/sruja-ai/srujaWrote 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/sruja-ai/sruja/sruja-dev)<a href="https://agentmods.dev/rules/sruja-ai/sruja/sruja-dev"><img src="https://agentmods.dev/badge/rules/sruja-ai/sruja/sruja-dev.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.00490 | $0.00490 |
| Opus 5 | $0.00245 | $0.00245 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
sruja-dev 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 4d 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
sruja-dev
Project context for Sruja core and extension development.
Scopes
**/*.rs**/*.ts**/*.sruja
Instructions
- Code Standards: Follow the conventions in
AGENTS.md. - Workflow: For non-trivial work, follow
AGENTS.mdsection AI agent workflow (multi-step tasks) — two-layer planning (scope vs task), artifact handoffs, fresh session after a frozen plan, and the system-evolution outer loop when agents miss conventions. - Architecture: Respect C4 boundaries declared in
.srujafiles. - WASM Integrity: If you modify
sruja-wasmorsruja-language, remind the user to rebuild WASM withjust wasm-nodejs(ormake wasm-nodejs) and update the extension assets. - Validation: Use
sruja linton any.srujafiles after editing.
Mandatory Gates
- Before non-trivial edits: Run
sruja focus --file <path>for task-scoped briefing. - Before marking done: Run
sruja verify-task --profile <coding|bugfix|review|arch> -r .. - When
.srujaor cross-crate imports change: Runsruja drift -r .andsruja intent check. - On verify failure: Fix the issue, re-verify, then record a correction learning via
sruja agent record.
Useful Context Tools
sruja focus --file <path>— Task-scoped briefing before deep edits.- Sruja MCP —
.cursor/mcp.json(SRUJA_MCP_WATCH_DRIFT=1). Seesruja-context-hostrule for drift, prune, memory. sruja drift— Check for drift after code edits.sruja memory search -r . "<query>"— Indexed learnings and context events.sruja why— Explain architectural relationships.
Repeatable flows
- Prefer Cursor project commands in
.cursor/commands/(seeAGENTS.md) over pasting the same long prompt repeatedly.
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.
- 4d ago First seen · 32 lines · 490 tokens per session scan A 4324800adcb8
sruja-dev is a cursor rule published in the GitHub repository sruja-ai/sruja (22 stars, last pushed 10d ago), licensed Apache-2.0. It adds 490 tokens to every session, about $0.0024 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-30.
Other cursor rules, from other repositories
laminar
Use it when user asks about adding instrumentation with Laminar, creating an eval with Laminar or migrating from Langfuse to Laminar instrumentation.
testing
Testing strategies and quality assurance — testing pyramid, unit/integration/E2E testing, TDD/BDD, test automation, and quality metrics. Applied when writing or reviewing tests.
api-design
API design guidelines — REST principles, GraphQL patterns, versioning, pagination, error handling, documentation, security, caching, and testing. Applied when designing or reviewing API endpoints.
owasp-ai-security-privacy
OWASP AI Security & Privacy Guide – PR rules emphasizing data protection, governance, and safety.
cursorrules
Cursor rule "cursorrules" from me2resh/agent-decision-record, covering agent decision records (agdr) — cursor rules, purpose, see: https://github.com/me2resh/agent-decision-record, decision detection and adding a new dependency → stop, document decision first.
agdr
Agent Decision Records - enforces structured documentation of technical decisions before implementation.