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/ddggkkcc/industry-intelligence-researcher/cursorrulesgit clone --depth 1 https://github.com/ddggkkcc/industry-intelligence-researcherWrote 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/ddggkkcc/industry-intelligence-researcher/cursorrules)<a href="https://agentmods.dev/rules/ddggkkcc/industry-intelligence-researcher/cursorrules"><img src="https://agentmods.dev/badge/rules/ddggkkcc/industry-intelligence-researcher/cursorrules.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.00207 | $0.00207 |
| Opus 5 | $0.00103 | $0.00103 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
cursorrules 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 4d 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
Cursor rules — Industry Intelligence Researcher
This project includes a sector-agnostic industry research methodology. The full instructions are in AGENTS.md in the project root.
Before starting any industry, market, competitive, value-chain, business-model, or investment research task:
- Read
AGENTS.mdand follow its research standard, 10-step workflow, output structure, and quality gate. - Use the templates in
templates/(research-brief, evidence-led-report, company-profile, interview-guide, data-ledger). - Consult the reference guides in
references/(source-hierarchy, business-models, practitioner-insight, research-quality) as needed. - See
examples/sector-agnostic-mini-study.mdfor a model of depth and citation discipline.
Core principles: define the market before collecting data; cite every material number; separate fact from inference; triangulate; label confidence; never fabricate sources; include business models and profit pools; use scenarios with falsifiers.
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.
- 4d ago First seen · 13 lines · 207 tokens per session scan A 9a109dccc499
cursorrules is a cursor rule published in the GitHub repository ddggkkcc/industry-intelligence-researcher (2 stars, last pushed 17d ago), licensed MIT. It adds 207 tokens to every session, about $0.0010 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.