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/actual-software/actual-cliWrote 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/actual-software/actual-cli/adr-003)<a href="https://agentmods.dev/rules/actual-software/actual-cli/adr-003"><img src="https://agentmods.dev/badge/rules/actual-software/actual-cli/adr-003/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/actual-software/actual-cli/adr-003"><img src="https://agentmods.dev/badge/rules/actual-software/actual-cli/adr-003.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.00000 | $0.00163 |
| Opus 5.5 | $0.00000 | $0.00065 |
| Sonnet 5.5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
adr-003 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 1mo 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
Adopt Comprehensive Unit Testing Strategy for CI/CD Pipeline Components
Policies
- Implement comprehensive unit testing for all CI/CD pipeline components and build tooling modules. Each module in the build, delivery, and tooling infrastructure must include unit tests that validate core functionality in isolation. This includes testing static analysis components (manifests, languages, registry), CLI command handlers (sync, auth, status), UI interaction components (confirm dialogs, file confirmations), generation and tailoring logic, signal processing (language resolver, tree-sitter, IR), API utilities (retry mechanisms), and configuration types. Unit tests should be co-located with source code or in parallel test directories, following Rust's standard testing conventions with #[cfg(test)] modules or separate test files.
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.
- 1mo ago First seen · 10 lines · 0 tokens per session scan A d1444e44a5d0
adr-003 is a cursor rule published in the GitHub repository actual-software/actual-cli (8 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 163 tokens. 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-31.
Other cursor rules, from other repositories
testing
Vitest testing patterns for Caliber.
unit-tests-todos
When proposing/writing unit test specs.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
testing
Testing rules for vitest suite.
api
For creating tests for the backend in bubblelab-api.
pytest-what-to-test-and-mocking
We mock external API calls (mark live tests with @pytest.mark.flaky()). We reuse fixtures from conftest.py. We always use pytest as testing framework - never import unittest. We use pytest-mock (mocker fixture) and monkeypatch for mocking, not unittest.mock.