Anima is an open-source local-network runtime that gives household hardware an AI layer for sensing environments, remembering preferences, planning actions, and controlling devices through adapters. It is intended for intelligent devices such as lights, air conditioners, humidifiers, air purifiers, and speakers, with a dashboard, REST API, and CLI for control and extension. The catalogue entries are skills, rules, and instructions for working with Anima.
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/migration-and-backward-compatibilitygit 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/migration-and-backward-compatibility)<a href="https://agentmods.dev/rules/fullive-ai/anima/migration-and-backward-compatibility"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/migration-and-backward-compatibility.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.00307 | $0.00307 |
| Opus 5 | $0.00153 | $0.00153 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
Migration-And-Backward-Compatibility 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 5d 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
Any change that affects stored data, config formats, message contracts, or upgrade paths must preserve compatibility or manage migration explicitly.
Core rule
Prefer backward-compatible evolution. If backward compatibility is not possible, implement a safe migration path.
Compatibility-sensitive areas
- persisted data
- database schemas
- config structures
- API contracts
- event schemas
- message payloads
- topic structures
- cache formats
- file formats
- serialized state
- user settings
- integration boundaries
Preferred approach
- make additive changes first
- support old and new formats during transition when feasible
- avoid instant hard breaks
- preserve existing behavior for existing consumers unless the task explicitly requires change
If a migration is needed
Do the following where applicable:
- identify what old state exists
- define the new target state
- provide a transition path
- update readers and writers consistently
- preserve idempotency when possible
- add migration or compatibility tests
- update docs and examples
Breaking compatibility
Only break compatibility when necessary.
If required:
- minimize the blast radius
- update all known dependents
- document the change clearly
- note any manual migration steps
- avoid partial migration states that are hard to recover from
Avoid
- silently changing formats
- upgrading only one side of a producer-consumer boundary
- assuming all existing data already matches the new model
- deleting compatibility code before consumers are updated
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.
- 5d ago First seen · 63 lines · 307 tokens per session scan A 73f0f553312e
Migration-And-Backward-Compatibility is a cursor rule published in the GitHub repository Fullive-AI/Anima (1,049 stars, last pushed 15d ago), licensed Apache-2.0. It adds 307 tokens to every session, about $0.0015 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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.