OpenContracts is an open-source document intelligence platform that turns document collections into searchable citation graphs with annotations, structured extraction, and AI agents. Builders and teams use it to work with unstructured documents through APIs, an MCP server, or a web interface. The catalogue entries extend the platform with agent, instruction, and rule workflows.
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/Open-Source-Legal/OpenContractsWrote 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/open-source-legal/opencontracts/running-frontend-tests)<a href="https://agentmods.dev/rules/open-source-legal/opencontracts/running-frontend-tests"><img src="https://agentmods.dev/badge/rules/open-source-legal/opencontracts/running-frontend-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/open-source-legal/opencontracts/running-frontend-tests"><img src="https://agentmods.dev/badge/rules/open-source-legal/opencontracts/running-frontend-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.00092 |
| Opus 5.5 | $0.00000 | $0.00037 |
| Sonnet 5.5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
running-frontend-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
Use yarn to run playwright tests with command yarn run test:ct --reporter=list. Using the list reported prevents the html results from rendering and hanging your tool. Obv you can use -g flag or specify test(s) names when running tests using this command syntax - no need to run the ENTIRE suite unless you have to.
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 · 7 lines · 0 tokens per session scan A 57511687a69f
running-frontend-tests is a cursor rule published in the GitHub repository Open-Source-Legal/OpenContracts (1,525 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 92 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
qa
Run the real app and drive the changed entry points (browser pages, API endpoints, CLI commands, jobs) the way a user would, then fix what breaks. Tests, triages by severity, fixes each issue with a regression test, re-verifies, and reports. Use after a feature is built, when asked to "QA this", "test the app", "check…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.