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/test-first-for-bugs-and-regression)<a href="https://agentmods.dev/rules/fullive-ai/anima/test-first-for-bugs-and-regression"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/test-first-for-bugs-and-regression.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.00332 | $0.00332 |
| Opus 5 | $0.00166 | $0.00166 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
Test-First-For-Bugs-And-Regression 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 7d 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
For bug fixes and regression-sensitive work, use tests to reproduce, protect, and verify behavior whenever practical.
Core rule
Do not just patch the symptom. First understand the failing behavior, then protect against its return.
Preferred workflow for bug fixes
- identify the failing behavior clearly
- locate or create the most targeted test that captures it
- confirm the failure when feasible
- implement the fix
- re-run the test
- run adjacent relevant checks to guard against regressions
Testing principles
- prefer targeted tests over broad blind runs at first
- add regression coverage for real bugs when practical
- test the root behavior, not just incidental implementation details
- include edge cases if they are directly related to the failure
- keep tests readable and aligned with project conventions
When adding a new test
Prefer tests that:
- fail before the fix
- pass after the fix
- clearly describe the intended behavior
- are narrow enough to diagnose future regressions quickly
If a test cannot be added immediately
Then still:
- document the failure mode clearly in your reasoning
- validate the fix using the strongest available check
- add a test if the codebase supports it and the scope allows it
Regression mindset
After fixing a bug, also consider:
- nearby code paths using the same logic
- boundary conditions
- serialization or interface effects
- consumer-facing side effects
- whether similar bugs could exist in sibling flows
Completion rule
A bug fix is stronger when it leaves behind proof that the bug will be caught if it returns.
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.
- 7d ago First seen · 58 lines · 332 tokens per session scan A 4f689c96e5ad
Test-First-For-Bugs-And-Regression is a cursor rule published in the GitHub repository Fullive-AI/Anima (1,049 stars, last pushed 17d ago), licensed Apache-2.0. It adds 332 tokens to every session, about $0.0017 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
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.