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/silenceinsect/aidocxworkflow/stage_s6_test_casesgit clone --depth 1 https://github.com/SilenceInsect/AIDocxWorkFlowWrote 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/silenceinsect/aidocxworkflow/stage_s6_test_cases)<a href="https://agentmods.dev/rules/silenceinsect/aidocxworkflow/stage_s6_test_cases"><img src="https://agentmods.dev/badge/rules/silenceinsect/aidocxworkflow/stage_s6_test_cases.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.00098 | $0.53570 |
| Opus 5 | $0.00049 | $0.26785 |
| Sonnet 5 | $0.00020 | $0.10714 |
| Haiku 4.5 | $0.00010 | $0.05357 |
Grade A, and why
STAGE_S6_TEST_CASES 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 770 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIDocxWorkFlow S6 â æµÂè¯Âç¨ä¾ÂçÂÂæÂÂ
ç¬ç«Âé¶段ï¼Âå¯以åÂÂç¬è°Âç¨ãÂÂä¸Â游æÂÂæÂÂï¼ÂS5 test_points.jsonï¼Â审æÂ¥åÂÂæ ¼åÂÂå¼Âå§Âï¼Â失败åÂÂ失败æÂ¥åÂÂãÂÂ
第ä¸ÂÃ¥ÂÂÃ¥ÂÂ
S6 å½ÂÃ¥ÂÂä¸Âæ¯å¨åÂÂ代ç Âå®Âç°ï¼Âä¹Âä¸Âæ¯å¨åÂÂæÂÂçÂÂçÂÂæ¡Âï¼ÂèÂÂæ¯å¨éÂÂÃ¥ÂÂéÂÂæ±Âè¦ÂçÂÂ缺å£ã é»Â认ç®æ Âä¸Âæ¯æÂÂå°Âç¨ä¾Âï¼ÂèÂÂæ¯åºäºÂ
coverage_ledger.jsonæ¾å¼Âå®ÂæÂÂè¦ÂçÂÂï¼Âä»»ä½ÂæªéÂÂÃ¥ÂÂç¹忠须è¿Âå ¥omission_ledger.jsonãÂÂ
é¶段堥å£
触åÂÂæ¹å¼Âï¼Â/aidocx-s6-test-cases æÂÂç²Âè´´ S5 test_points.json
Ã¥ÂÂç½®æÂÂæÂÂï¼Â忠须堨é¨满足ï¼Âï¼Â
| æÂÂæ | æ¥溠| 审æÂ¥è¦Âæ± |
|---|---|---|
| S5 test_points.jsonï¼Â忠须读åÂÂï¼ | workflow_assets/<req_name>/<version>/ãÂÂS5 æµÂè¯Âç¹çÂÂæÂÂãÂÂ/test_points.json |
æ¯Â个 TP å« module / test_point_type |
| S2 backlogï¼Â忠须读åÂÂï¼ | workflow_assets/<req_name>/<version>/ãÂÂS2 éÂÂæ±ÂæÂÂ解ãÂÂ/backlog.md |
ä½Â为ä¼Âå Â级åÂÂè |
| S4 business_flow.mdï¼Â忠须读åÂÂï¼ | workflow_assets/<req_name>/<version>/ãÂÂS4 æµÂç¨Âå¾导åºãÂÂ/business_flow.md |
ç¨äºÂçÂÂ解ä¸Âå¡æµÂç¨ÂÃ¥ÂÂé£Âé©åºæ¯ |
| 模åÂÂÃ¥ÂÂ模æ¿ï¼Â忠须读åÂÂï¼ | knowledge/public/module_templates/ï¼Âæ TP ç module Ã¥ÂÂ段＠|
æ¯Â个模åÂÂçÂÂÃ¥ÂÂç±»æÂÂ举å³宠TC æ¹æ³ÂéÂÂæ© |
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.
- 3d ago First seen · 770 lines · 53,570 tokens per session scan A 905c91646d97
STAGE_S6_TEST_CASES is a cursor rule published in the GitHub repository SilenceInsect/AIDocxWorkFlow (2 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 53,570 once invoked, about $0.0005 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.