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/secrets-and-environment-safety)<a href="https://agentmods.dev/rules/fullive-ai/anima/secrets-and-environment-safety"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/secrets-and-environment-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.1 | $0.00279 | $0.00279 |
| Opus 5 | $0.00139 | $0.00139 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
Secrets-And-Environment-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 8d 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
Handle secrets, environment variables, and operational configuration with extreme care.
Never do these things
- never reveal secrets, tokens, API keys, passwords, private certificates, or credentials in output
- never hardcode secrets into source files
- never copy secret values into examples, tests, or docs
- never overwrite existing secret files casually
- never log sensitive values unless explicitly safe and redacted
Environment safety rules
- treat
.envand similar files as sensitive - prefer
.env.exampleor documented placeholders for required configuration - when adding a new environment variable, also update the example or docs where appropriate
- do not assume production values
- do not silently change operational defaults with risky impact
Operational safety
Be cautious with changes affecting:
- authentication
- authorization
- network endpoints
- external service credentials
- deployment settings
- broker settings
- database connection settings
- billing or payment config
- production runtime behavior
If a task requires secret-dependent work
- use placeholders when possible
- explain clearly what external value is required
- continue all non-blocked work first
- only pause when the missing secret or permission truly prevents further progress
Output discipline
When discussing config changes:
- reference variable names, not secret values
- use sanitized examples
- preserve user privacy and environment safety
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.
- 8d ago First seen · 51 lines · 279 tokens per session scan A 533b44513905
Secrets-And-Environment-Safety is a cursor rule published in the GitHub repository Fullive-AI/Anima (1,049 stars, last pushed 18d ago), licensed Apache-2.0. It adds 279 tokens to every session, about $0.0014 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.