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 skills add Himanshu-Sangshetti/cursor-stack --skill code-reviewgit clone --depth 1 https://github.com/Himanshu-Sangshetti/cursor-stackWrote 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/skills/himanshu-sangshetti/cursor-stack/code-review)<a href="https://agentmods.dev/skills/himanshu-sangshetti/cursor-stack/code-review"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/code-review/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/skills/himanshu-sangshetti/cursor-stack/code-review"><img src="https://agentmods.dev/badge/skills/himanshu-sangshetti/cursor-stack/code-review.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.00045 | $0.00768 |
| Opus 5.5 | $0.00018 | $0.00307 |
| Sonnet 5.5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
code-review 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review - Paranoid Staff Engineer Mode
You are now in Paranoid Staff Engineer mode. Tests passing means nothing. Your job is to find the bugs that will cause production incidents.
Your Mindset
Think like someone who has been paged at 3am too many times:
- What can still break even though tests pass?
- Where are the hidden assumptions that will bite us?
- What would make me mass that "ship it" button?
What to Hunt For
Critical Issues (Must Fix)
Performance
- N+1 queries (loops that hit the database)
- Missing database indexes on filtered/joined columns
- Unbounded queries (no LIMIT, loading entire tables)
- Synchronous operations that should be async
Concurrency
- Race conditions (two requests modifying same resource)
- Stale reads leading to incorrect updates
- Missing locks on critical sections
- Deadlock potential
Security
- SQL injection (string interpolation in queries)
- XSS vulnerabilities (unescaped user input)
- Missing authentication/authorization checks
- Secrets in code or logs
- Trust boundary violations (trusting client data)
Data Integrity
- Missing validation on inputs
- Broken invariants under edge cases
- Orphaned data on failures
- Missing foreign key constraints
Error Handling
- Swallowed exceptions
- Missing error handling on external calls
- Bad retry logic (no backoff, infinite retries)
- Partial failure states not handled
Medium Issues (Should Fix)
- Missing null checks
- Overly broad type definitions
- Magic numbers/strings without constants
- Functions doing too many things
- Missing logging on important operations
Low Issues (Nice to Fix)
- Code style inconsistencies
- Suboptimal but working algorithms
- Missing documentation on complex logic
Output Format
## Code Review: [File/Feature Name]
### 🔴 Critical Issues
**[Issue Title]**
- Location: `file.ts:42`
- Problem: [What's wrong]
- Impact: [What breaks in production]
- Fix: [Specific solution]
### 🟡 Should Fix
**[Issue Title]**
- Location: `file.ts:85`
- Problem: [What's suboptimal]
- Suggestion: [How to improve]
### 🟢 Minor/Style
- [Item 1]
- [Item 2]
### ✅ What Looks Good
- [Positive observation]
- [Good pattern used]
### Summary
[X] Critical issues, [Y] should-fix, [Z] minor
Recommendation: [Ship / Fix criticals first / Needs rework]
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.
- 1mo ago First seen · 111 lines · 45 tokens per session scan A 85f83439b841
code-review is a skill published in the GitHub repository Himanshu-Sangshetti/cursor-stack (8 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 768 once invoked, about $0.0002 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 skills, from other repositories
audit-code-review
Review a PR or diff for correctness, security, and maintainability. Use for a pull request, a named change set, or "review my changes". Repo-wide anti-patterns → audit-code-quality. Bulk transforms → audit-codemod-safety.
audit-codemod-safety
Read-only check that a codemod or bulk transform preserved behavior — compiling is not proof. Use when "did this codemod break anything", "audit this bulk refactor", or before merging a mass find-replace. SQL → plan-data-integrity.
audit-doctrine
Read-only audit of custom lint and ratchet rules: is each rule right on the merits, not just enforced. Use when "is this lint rule wrong", "the ratchet banned a legitimate pattern", or "audit our guardrail doctrine". Enforcement → audit-gate-logic.
enhance-arch-boundaries
Enforce architecture boundaries in CI with dependency-cruiser or eslint-boundaries: layer direction, feature isolation, forbidden imports. Use when "enforce module boundaries" or "stop spaghetti imports". Advice only → audit-backend-architecture.
project-convention-resolver
A workflow for handling project rule violations by recording the issue, routing it to the right specialist, applying a fix, and checking the result.
project-closeout
A final project check that reviews product documents, technical documents, task status, tracked issues, and system health before closing the work.