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.
git 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/repo-navigation-and-module-ownership)<a href="https://agentmods.dev/rules/fullive-ai/anima/repo-navigation-and-module-ownership"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/repo-navigation-and-module-ownership/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/fullive-ai/anima/repo-navigation-and-module-ownership"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/repo-navigation-and-module-ownership.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.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
Repo-Navigation-And-Module-Ownership 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 10d 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
Before editing, orient yourself in the repository and identify the correct ownership boundary.
Required behavior
For each task:
- Determine which module, package, app, service, or subsystem owns the change.
- Inspect the nearest relevant files before making edits.
- Follow local conventions in that part of the repo.
- Limit changes to the owning area unless downstream or upstream compatibility requires more.
Navigation principles
- Start from the entry point most relevant to the request.
- Trace usage through imports, calls, routes, handlers, adapters, and tests.
- Prefer modifying the true owner of the behavior, not a random nearby consumer.
- Avoid scattering a single concern across multiple modules.
Ownership rules
- Put business logic in the business logic owner.
- Put UI behavior in the UI owner.
- Put integration glue in the integration owner.
- Put protocol handling in the protocol owner.
- Put tests next to or clearly aligned with the owning behavior.
Cross-module changes
If multiple modules must change:
- Identify the dependency chain first.
- List the affected boundaries mentally before editing.
- Keep the interface between modules clear.
- Change only the modules necessary to complete the task safely.
Avoid
- editing whichever file appears first in search results without understanding ownership
- patching symptoms in consumers when the root cause belongs in a shared owner
- creating shadow logic in a second module
- spreading fixes across the repo without a clear dependency reason
Preferred mindset
Understand where the change belongs before deciding how to implement it.
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.
- 10d ago First seen · 50 lines · 320 tokens per session scan A 0b99e9acf828
Repo-Navigation-And-Module-Ownership is a cursor rule published in the GitHub repository Fullive-AI/Anima (1,046 stars, last pushed 20d 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.