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/radiantlogicinc/fastworkflowWrote 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/radiantlogicinc/fastworkflow/testing_rules)<a href="https://agentmods.dev/rules/radiantlogicinc/fastworkflow/testing_rules"><img src="https://agentmods.dev/badge/rules/radiantlogicinc/fastworkflow/testing_rules/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/radiantlogicinc/fastworkflow/testing_rules"><img src="https://agentmods.dev/badge/rules/radiantlogicinc/fastworkflow/testing_rules.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.00228 | $0.00228 |
| Opus 5.5 | $0.00091 | $0.00091 |
| Sonnet 5.5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
testing_rules 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
Testing Patterns for FastWorkflow
- Don't use Mock fixtures. All our tests are integration tests
- Do not remove pytest tests without explicit user approval
MCP Integration Testing
Test Structure
- ./tests - Folder with all the tests
- tests/conftest.py - Pytest configuration and shared fixtures
- tests/README.md - Testing documentation and usage guide
Testing Best Practices
Integration Testing Philosophy
# ✅ DO: Use real test workflows
workflow_path = os.path.join("tests", "example_workflow")
workflow_path = os.path.join("tests", "hello_world_workflow")
# ✅ DO: Test end-to-end functionality
result = mcp_server.call_tool("get_user_details", {"user_id": "sara_doe_496"})
# ❌ DON'T: Mock FastWorkflow components
# ❌ DON'T: Use fake data when real data is available
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 · 31 lines · 228 tokens per session scan A f749af0a8ed1
testing_rules is a cursor rule published in the GitHub repository radiantlogicinc/fastworkflow (52 stars, last pushed 6d ago), licensed Apache-2.0. It adds 228 tokens to every session, about $0.0009 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
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.