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/osaurus-ai/osaurus/testing-workflowgit clone --depth 1 https://github.com/osaurus-ai/osaurusWhat 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.00278 | $0.00278 |
| Opus 5 | $0.00139 | $0.00139 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
testing-workflow 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 yesterday.
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
Testing Workflow
The full unit suite (make test, ~5000 tests) takes about 30 minutes. Do NOT
run it during normal development iterations.
During development
- Run only targeted tests scoped to what you changed, using
--filter:
OSAURUS_DISABLE_KEYCHAIN_FOR_TESTS=1 \
OSAURUS_TEST_ROOT=/tmp/osaurus-test \
OSU_MODELS_DIR=/tmp/osaurus-test-models \
swift test --package-path Packages/OsaurusCore --filter "SuiteOrTestName"
- A plain
swift build --package-path Packages/OsaurusCoreis enough to verify compilation after edits.
Before submitting a PR
- Run the full suite exactly once, right before the PR is created:
OSAURUS_DISABLE_KEYCHAIN_FOR_TESTS=1 \
OSAURUS_TEST_ROOT=/tmp/osaurus-test \
OSU_MODELS_DIR=/tmp/osaurus-test-models \
make test
- Keychain-gated suites (e.g.
PluginAgentScopingTests) fail by design underOSAURUS_DISABLE_KEYCHAIN_FOR_TESTS=1; run those without the flag when their area was touched.
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.
- yesterday First seen · 39 lines · 278 tokens per session scan A 7c1df8727cd7
testing-workflow is a cursor rule published in the GitHub repository osaurus-ai/osaurus (7,740 stars, last pushed yesterday), licensed MIT. It adds 278 tokens to every session, about $0.0014 per session on Opus 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
create-ios-release
As an AI assistant helping with iOS app releases, I should guide through the following process for successfully deploying iOS applications to the App Store.
on-load-rule
This guide outlines the critical development principles for this Swift project.
knowledge-management-rule
Comprehensive knowledge management system for capturing, organizing, and applying project knowledge.
specification-management-rule
Comprehensive specification management system for creating, validating, and tracking requirements.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.
location-rule
Rules for placing and organizing Cursor rule files in the repository.