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/license-and-dependency-compliance)<a href="https://agentmods.dev/rules/fullive-ai/anima/license-and-dependency-compliance"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/license-and-dependency-compliance/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/license-and-dependency-compliance"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/license-and-dependency-compliance.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.00062 | $0.00062 |
| Opus 5 | $0.00031 | $0.00031 |
| Sonnet 5 | $0.00012 | $0.00012 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
License-And-Dependency-Compliance 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 9d 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
Be careful with dependencies, copied code, and license implications.
Prefer existing project dependencies and patterns when reasonable. When adding or updating dependencies, keep the change intentional, minimal, and consistent with the project.
Avoid unclear provenance, unnecessary dependency bloat, and unrelated lockfile churn.
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.
- 9d ago First seen · 11 lines · 62 tokens per session scan A ecbb296b9789
License-And-Dependency-Compliance is a cursor rule published in the GitHub repository Fullive-AI/Anima (1,049 stars, last pushed 20d ago), licensed Apache-2.0. It adds 62 tokens to every session, about $0.0003 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
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
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.