Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rulesnpx agentmods add rules/charlee-x/effect-cursor-rules/api-client-testingWrote 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/charlee-x/effect-cursor-rules/api-client-testing)<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/api-client-testing"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/api-client-testing/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/charlee-x/effect-cursor-rules/api-client-testing"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/api-client-testing.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.01387 |
| Opus 5.5 | $0.00000 | $0.00555 |
| Sonnet 5.5 | $0.00000 | $0.00277 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
api-client-testing 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.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Client Testing Patterns
Required Imports for API Client Tests
import { describe, expect, it } from '@effect/vitest'
import { FetchHttpClientTest, getExitError } from '@t6c/lib-api'
import { Effect as E, Exit } from 'effect'
import { MockConfigLayer } from '../config.js'
Standard API Client Test Structure
Success Test Pattern
it.effect('should [action description]', () =>
E.gen(function* () {
const service = yield* ServiceName
const result = yield* service.methodName(params)
expect(result).toEqual(expectedResult)
}).pipe(
E.provide(ServiceName.DefaultWithoutDependencies),
E.provide(
FetchHttpClientTest(
new Response(JSON.stringify(mockResponse), { status: 200 }),
),
),
E.provide(MockConfigLayer),
),
)
Error Test Pattern (PREFERRED)
it.effect('should handle [error type]', () =>
E.gen(function* () {
const service = yield* ServiceName
const result = yield* service
.methodName(params)
.pipe(E.exit)
expect(Exit.isFailure(result)).toBe(true)
const error = getExitError(result)
expect(error?._tag).toBe('ExpectedErrorType')
}).pipe(
E.provide(ServiceName.DefaultWithoutDependencies),
E.provide(FetchHttpClientTest(new Response(null, { status: 404 }))),
E.provide(MockConfigLayer),
),
)
Variable Scoping Rules
CRITICAL: Variables Used in FetchHttpClientTest
- ALWAYS declare variables outside the generator function if they're used in
FetchHttpClientTest - This prevents scoping issues where variables are not accessible
// ✅ CORRECT
it.effect('should update resource', () => {
const updatedResource = { ...mockResource, field: 'new value' }
return E.gen(function* () {
const service = yield* ServiceName
const result = yield* service.update(id, updates)
expect(result).toEqual(updatedResource)
}).pipe(
E.provide(ServiceName.DefaultWithoutDependencies),
E.provide(
FetchHttpClientTest(
new Response(JSON.stringify(updatedResource), { status: 200 }),
),
),
E.provide(MockConfigLayer),
)
})
// ❌ WRONG - Variable not accessible in FetchHttpClientTest
it.effect('should update resource', () =>
E.gen(function* () {
const updatedResource = { /* ... */ } // Scoping issue!
// ...
}).pipe(
E.provide(
FetchHttpClientTest(
new Response(JSON.stringify(updatedResource), { status: 200 }), // Error!
),
),
),
)
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 · 216 lines · 1,387 tokens per session scan A c92ad1d112c4
api-client-testing is a cursor rule published in the GitHub repository CharLEE-X/effect-cursor-rules (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,387 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
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.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
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.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.