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.
npx agentmods add rules/lineai-intelligence/lineai-mcp-server/testing-approachgit clone --depth 1 https://github.com/lineai-intelligence/lineai-mcp-serverWrote 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/lineai-intelligence/lineai-mcp-server/testing-approach)<a href="https://agentmods.dev/rules/lineai-intelligence/lineai-mcp-server/testing-approach"><img src="https://agentmods.dev/badge/rules/lineai-intelligence/lineai-mcp-server/testing-approach.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 | $0.00000 | $0.00074 |
| Opus 5 | $0.00000 | $0.00037 |
| Sonnet 5 | $0.00000 | $0.00015 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
testing-approach 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 4d 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
- Use unit tests for functions without external dependencies
- Use integration tests for tests against a real Lineai server
- Set the
LINEAI_TEST_MODEenvironment variable for test runs - Test both success cases and error handling patterns
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.
- 4d ago First seen · 9 lines · 0 tokens per session scan A 30a79676640f
testing-approach is a cursor rule published in the GitHub repository lineai-intelligence/lineai-mcp-server (38 stars, last pushed 22d ago), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 74 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-30.
Other cursor rules, from other repositories
testing
Testing strategy for AI developers.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
testing
Vitest conventions and the mandatory unit-test set.
testing
Vitest and Playwright BDD testing conventions.
do-runner
Use the following runners.
tester
Tester role - Unit, E2E, and visual regression testing.