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/qwickapps/ai-sdlc-workflowsWrote 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/qwickapps/ai-sdlc-workflows/fact-verification)<a href="https://agentmods.dev/rules/qwickapps/ai-sdlc-workflows/fact-verification"><img src="https://agentmods.dev/badge/rules/qwickapps/ai-sdlc-workflows/fact-verification/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/qwickapps/ai-sdlc-workflows/fact-verification"><img src="https://agentmods.dev/badge/rules/qwickapps/ai-sdlc-workflows/fact-verification.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.01312 | $0.01312 |
| Opus 5.5 | $0.00525 | $0.00525 |
| Sonnet 5.5 | $0.00262 | $0.00262 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
FACT-VERIFICATION 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 2mo 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fact Verification Rules
When to apply: Before making any claim in spikes, reports, documentation, or JIRA comments.
Core Principle
Every factual claim must be verifiable with evidence.
No assumptions presented as facts. No unverified claims. No "probably" or "should" without explanation.
Reference: See COMMON-PATTERNS.md § Evidence Requirements for detailed standards.
What Requires Verification
All Claims About:
- Version numbers and release dates
- File locations and line numbers
- API behavior and requirements
- Compatibility and incompatibility
- Breaking changes
- Plugin/library features
- Performance characteristics
- Security implications
Requires Verification:
- "Plugin X is compatible with Platform Y"
- "File path is /path/to/file"
- "Function Z was deprecated in version 2.0"
- "This change will break existing code"
Does NOT Require Verification:
- Recommendations based on verified facts
- Process descriptions
- Explanations of verified findings
Verification Methods
Code-Based Claims
Claim Type: File exists, code contains X, function does Y
Methods:
- Read the actual file
- Quote the relevant code
- Provide file path and line numbers
Example:
Claim: Hook references project name variable
Verification: Read hooks/after_prepare_ios.js
Evidence: Line 4: var project = process.env.project
Status: VERIFIED
Version Claims
Claim Type: Package version, release date, requirements
Methods:
- Read package.json, plugin.xml, or equivalent
- Check official release announcements
- Inspect package registry (npm, PyPI)
Compatibility Claims
Claim Type: X works/doesn't work with Y
Methods:
- Check engine requirements (plugin.xml, package.json)
- Read documentation for compatibility notes
- Search issue trackers for known problems
- Inspect source code for API usage
- Test if necessary
API/Feature Claims
Claim Type: API X does Y, Feature Z requires W
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.
- 2mo ago First seen · 227 lines · 1,312 tokens per session scan A 17ad34051c33
FACT-VERIFICATION is a cursor rule published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 1,312 tokens to every session, about $0.0052 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-31.
Other cursor rules, from other repositories
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.