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/tugkanboz/awesome-cursorrulesWrote 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/tugkanboz/awesome-cursorrules/api-testing)<a href="https://agentmods.dev/rules/tugkanboz/awesome-cursorrules/api-testing"><img src="https://agentmods.dev/badge/rules/tugkanboz/awesome-cursorrules/api-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/tugkanboz/awesome-cursorrules/api-testing"><img src="https://agentmods.dev/badge/rules/tugkanboz/awesome-cursorrules/api-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.02697 | $0.02697 |
| Opus 5.5 | $0.01079 | $0.01079 |
| Sonnet 5.5 | $0.00539 | $0.00539 |
| Haiku 4.5 | $0.00270 | $0.00270 |
Grade A, and why
api-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- network-api-testing — 88% identical, 67 lines differ
How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cypress API Testing Excellence
Network Interception Mastery
- Request/Response Mocking: Control external API responses for reliable testing
- Network Monitoring: Track and validate API calls during user interactions
- Error Simulation: Test error handling and edge cases
- Performance Testing: Monitor response times and optimize user experience
Advanced API Interception
// ✅ Comprehensive API interception setup
describe('API Integration Tests', () => {
beforeEach(() => {
// Set up common API routes
cy.intercept('GET', '/api/users*', { fixture: 'users.json' }).as('getUsers')
cy.intercept('POST', '/api/users', { fixture: 'user-created.json' }).as('createUser')
cy.intercept('PUT', '/api/users/*', { fixture: 'user-updated.json' }).as('updateUser')
cy.intercept('DELETE', '/api/users/*', { statusCode: 204 }).as('deleteUser')
})
it('should handle complete user CRUD operations', () => {
// Visit page and wait for initial data load
cy.visit('/users')
cy.wait('@getUsers').then((interception) => {
expect(interception.response.statusCode).to.equal(200)
expect(interception.response.body).to.have.property('users')
})
// Create new user
cy.get('[data-cy=add-user-button]').click()
cy.get('[data-cy=user-form]').within(() => {
cy.get('[data-cy=first-name]').type('John')
cy.get('[data-cy=last-name]').type('Doe')
cy.get('[data-cy=email]').type('[email protected]')
cy.get('[data-cy=submit-button]').click()
})
cy.wait('@createUser').then((interception) => {
expect(interception.request.body).to.deep.include({
firstName: 'John',
lastName: 'Doe',
email: '[email protected]'
})
expect(interception.response.statusCode).to.equal(201)
})
// Verify user appears in list
cy.get('[data-cy=user-list]')
.should('contain.text', 'John Doe')
.and('contain.text', '[email protected]')
})
})
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 · 340 lines · 2,697 tokens per session scan A 1c1ca4e284e1
api-testing is a cursor rule published in the GitHub repository tugkanboz/awesome-cursorrules (22 stars, last pushed 17d ago), licensed MIT. It adds 2,697 tokens to every session, about $0.0108 per session on Opus 5.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
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
unity-testing
Unity Test Framework (Production Standards).
testing
Testing: test design, mocking strategy, coverage philosophy.
jest
Jest: describe/it, matchers, mocking, async testing.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
vitest
Vitest: unit testing, mocking, coverage, snapshot testing.