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/qwickapps/ai-sdlc-workflows/research-depthgit clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsWhat 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.01884 | $0.01884 |
| Opus 5 | $0.00942 | $0.00942 |
| Sonnet 5 | $0.00377 | $0.00377 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
RESEARCH-DEPTH 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.
How it starts
The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Depth Requirements
When to apply: Before making assumptions, before implementing solutions, during investigation phases.
Core Principle
Do NOT make assumptions. Use available research tools to gather evidence BEFORE acting.
You have powerful research tools (Explore agent, Grep, Chrome automation, QwickBrain MCP). Use them. Shallow research leads to wrong assumptions and wasted effort.
Reference: See COMMON-PATTERNS.md for evidence requirements and research documentation patterns.
Research Tools Available
1. Explore Agent
Task tool with subagent_type=Explore
When to use:
- Exploring unfamiliar codebase
- Finding patterns/conventions/existing implementations
- Understanding "how does X work?"
- Locating files by functionality (not exact name)
Example prompts:
- "Find how authentication is implemented"
- "Explore migration system and how it loads files"
- "Find error handling patterns in API endpoints"
Do NOT:
- Search manually with multiple Grep commands
- Make assumptions about architecture
- Guess where code might be
2. Grep (Content Search)
When to use:
- Finding specific code patterns, function names, strings
- Searching for exact matches
- Finding usages of function/variable
Example patterns:
pattern: "import.*PayloadConfig"pattern: "migration\.up"pattern: "class.*Migration"
Do NOT:
- Use for open-ended exploration (use Explore)
- Search without specific pattern
3. Chrome Automation
Tools: mcp__claude-in-chrome__*
When to use:
- Testing web applications
- Verifying frontend functionality
- Capturing UI state/errors
- Recording user workflows
- Checking browser console for errors
Key operations:
tabs_context_mcp- Get current tabstabs_create_mcp- Create new tabscreenshot- Capture stateread_console_messages- Check errorsgif_creator- Record interactions
Do NOT:
- Assume frontend works without browser check
- Skip console error checks
- Trigger JavaScript alerts (blocks extension)
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 · 342 lines · 1,884 tokens per session scan A 01cce406e560
RESEARCH-DEPTH is a cursor rule published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,884 tokens to every session, about $0.0094 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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.