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/fullive-ai/anima/dependency-and-interface-safetygit clone --depth 1 https://github.com/Fullive-AI/AnimaWrote 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/fullive-ai/anima/dependency-and-interface-safety)<a href="https://agentmods.dev/rules/fullive-ai/anima/dependency-and-interface-safety"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/dependency-and-interface-safety.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.00320 | $0.00320 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
Dependency-And-Interface-Safety 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
Treat shared interfaces, schemas, contracts, and dependency relationships as high-sensitivity areas.
Core rule
Before changing an interface, find who depends on it.
Interfaces include
- public functions
- exported types
- module contracts
- API request and response shapes
- event payloads
- message formats
- topic names
- config structures
- CLI arguments
- database-facing schemas
- file formats
Required behavior before changing an interface
Identify:
- producers
- consumers
- callers
- downstream dependents
- test coverage around the contract
- whether the change is backward compatible
Preferred approach
- preserve backward compatibility by default
- prefer additive changes over breaking changes
- update all affected callers when a contract must change
- keep dependency relationships clear and stable
- avoid hidden contract drift
Breaking changes
Only make a breaking change when clearly necessary.
If required:
- minimize the blast radius
- update all affected code paths
- update tests
- update docs
- call out the compatibility impact explicitly in your summary
Dependency safety
- do not create circular dependencies
- do not introduce a new dependency for a trivial local need
- prefer existing project patterns and libraries
- avoid tight coupling between unrelated modules
- keep abstractions honest and narrow
Avoid
- changing one side of an interface without updating the other side
- silently altering payload meanings
- reusing a contract for a different semantic purpose
- weakening types or schemas just to make code compile
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 · 70 lines · 320 tokens per session scan A 0e23c064c4f3
Dependency-And-Interface-Safety is a cursor rule published in the GitHub repository Fullive-AI/Anima (1,049 stars, last pushed 14d ago), licensed Apache-2.0. It adds 320 tokens to every session, about $0.0016 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.