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/Sourcery-info/barracuda-mcpWrote 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/sourcery-info/barracuda-mcp/typescript-tests)<a href="https://agentmods.dev/rules/sourcery-info/barracuda-mcp/typescript-tests"><img src="https://agentmods.dev/badge/rules/sourcery-info/barracuda-mcp/typescript-tests/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/sourcery-info/barracuda-mcp/typescript-tests"><img src="https://agentmods.dev/badge/rules/sourcery-info/barracuda-mcp/typescript-tests.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.00235 |
| Opus 5.5 | $0.00000 | $0.00094 |
| Sonnet 5.5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
typescript-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 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
TypeScript and tests
- Use Vitest for unit tests. Place tests under
test/as*.test.ts. - Do not hit real OpenAleph in unit tests: mock
fetchwithvitestvi.fn, inject a stub client, or use MSW if you add HTTP-level integration tests. - End-to-end tests against a real instance live in
test/e2e/*.e2e.test.tsand run withnpm run test:e2e(loads.envviatest/e2e/setup-env.ts). Defaultnpm testexcludes that folder. - Test URL/query construction and error mapping (
AlephHttpError, timeouts) explicitly. - Export thin functions for tool execution (e.g.
runAlephSearchTool) when it improves testability without widening the public MCP surface. - Match existing style: ESM,
NodeNextresolution, strict TypeScript, explicit return types on public exports where it helps readability.
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 · 15 lines · 0 tokens per session scan A 7c30c0b9fe30
typescript-tests is a cursor rule published in the GitHub repository Sourcery-info/barracuda-mcp (1 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 235 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
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
fix-galo
SYNTAX RULES.
testing
Cursor rule "testing" from andersonlemesc/Oryntra, covering testes oryntra, laravel (pest), python (pytest), contract tests (laravel ↔ python) and browser/e2e.