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/promptly-technologies-llc/fastapi-jinja2-postgres-webapp/routers_testsgit clone --depth 1 https://github.com/Promptly-Technologies-LLC/fastapi-jinja2-postgres-webappWrote 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/promptly-technologies-llc/fastapi-jinja2-postgres-webapp/routers_tests)<a href="https://agentmods.dev/rules/promptly-technologies-llc/fastapi-jinja2-postgres-webapp/routers_tests"><img src="https://agentmods.dev/badge/rules/promptly-technologies-llc/fastapi-jinja2-postgres-webapp/routers_tests.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.00154 |
| Opus 5 | $0.00000 | $0.00077 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
routers_tests 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
Setting test expectations regarding HTTP status codes
Since this is a FastAPI web application, test logic for API endpoints often involves checking status codes. Remember, when making a request to an API endpoint, you should specify the follow_redirects parameter. With follow_redirects=False, the response code will often be 303; otherwise it will be the response code of the route we've redirected to. We mostly use follow_redirects=False so as to test routes in isolation, but there may be test cases where following the redirect is more appropriate.
When checking status codes, think carefully to make sure the expected status code is the most appropriate to the situation.
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 · 11 lines · 0 tokens per session scan A 32ef4a986f54
routers_tests is a cursor rule published in the GitHub repository Promptly-Technologies-LLC/fastapi-jinja2-postgres-webapp (10 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 154 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
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
web-pages-e2e-test-maintenance
Keep web pages end-to-end coverage current.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
xiigen-user-journey-testing
Validate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.