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/emissium/cursor-rules/first-look-analysisgit clone --depth 1 https://github.com/emissium/cursor-rulesWhat 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.00012 | $0.00419 |
| Opus 5 | $0.00006 | $0.00210 |
| Sonnet 5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
first-look-analysis 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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is your first time seeing this repository. Perform a deep-drive into the codebase, the logic, the architecture, and the details of the project. Write a detailed report on your findings. Make sure to build up a robust context of the project, its purpose, and how it works.
First Look Report
Overview
Provide a brief summary of the project, its main features, and its intended use case.
Architecture
Describe the overall architecture of the project. Include details about the main components, how they interact, and any architectural patterns used (e.g., MVC, microservices).
Code Structure
Outline the structure of the codebase. Discuss the organization of files and directories, naming conventions, and any notable patterns in the code organization.
Key Components
Identify and describe the key components of the project. Discuss their roles, how they interact with each other, and any dependencies they have.
Logic and Algorithms
Discuss the main logic and algorithms used in the project. Highlight any complex algorithms, data structures, or design patterns that are employed.
Dependencies
List the main dependencies of the project. Include libraries, frameworks, and any external services that the project relies on. Discuss how these dependencies are managed (e.g., package managers, version control).
Testing
Describe the testing strategy used in the project. Include details about unit tests, integration tests, and any testing frameworks employed. Discuss the coverage of tests and how they contribute to the reliability of the codebase.
Documentation
Discuss the documentation provided with the project. Include details about inline comments, README files, and any external documentation resources. Evaluate the clarity and completeness of the documentation.
Areas for Improvement
Identify any areas where the project could be improved. This could include code quality, performance optimizations, better documentation, or additional features.
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.
- 2d ago First seen · 49 lines · 12 tokens per session scan A 50f272820d56
first-look-analysis is a cursor rule published in the GitHub repository emissium/cursor-rules (7 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 419 once invoked, about $0.0001 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.