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/boona13/ivn/ivn-knowledgegit clone --depth 1 https://github.com/boona13/ivnWhat 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.00264 | $0.00264 |
| Opus 5 | $0.00132 | $0.00132 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
ivn-knowledge 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
Project Knowledge (via ivn)
Auto-generated by
ivn sync-rules. Do not edit manually.
Project Context
- The compatibility suite keeps adapters honest.
Architectural Decisions
These decisions have been made. Follow them consistently:
- We decided every exported rule file should be fixture-tested.
Coding Patterns & Conventions
Always follow these established patterns:
- We use adapter registries instead of monolithic sync files.
Known Gotchas & Pitfalls
Be aware of these issues. Warn the developer if relevant:
- ⚠ Watch out: managed markdown blocks must preserve user-written content.
Dependencies & Constraints
- This depends on stable spec versions and deterministic markdown output.
Active Work & TODOs
- Add more fixture projects for future adapters.
Capture New Knowledge
When you discover something important while working — a decision, gotcha, bug fix, or pattern — persist it so future sessions already know:
ivn remember "what you learned and WHY" --type gotcha --tags relevant,tags
Types: decision · pattern · gotcha · debug · dependency · todo
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 · 50 lines · 264 tokens per session scan A ef0840e647cf
ivn-knowledge is a cursor rule published in the GitHub repository boona13/ivn (2 stars, last pushed 2mo ago), licensed MIT. It adds 264 tokens to every session, about $0.0013 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.