tech-stack

Project rules for a JavaScript or Node.js project that uses pnpm, a package manager for installing libraries, and a specified Node.js version. They document common commands and dependency-management practices.

In plain words
What is it for?
Use them when installing dependencies, adding packages, running project scripts, or checking the expected Node.js and pnpm setup.
Why use it?
They reduce uncertainty about which tools and commands the project expects and help prevent code from using packages that were not explicitly declared.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/yu-iskw/skill-inspector/tech-stack
Clone the repo
git clone --depth 1 https://github.com/yu-iskw/skill-inspector

Made for: Cursor.

Per session 192 This file is loaded in full into every session.
When invoked 192 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00192 $0.00192
Opus 5 $0.00096 $0.00096
Sonnet 5 $0.00038 $0.00038
Haiku 4.5 $0.00019 $0.00019

Measured yesterday against content hash 626d6ac71534, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tech-stack 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.

.cursor/rules/tech-stack.mdc · 28 lines

What it actually says

Tech Stack

This project uses:

pnpm Best Practices

Common Commands

  • Install All Dependencies: pnpm install
  • Add Dependency:
    • To package: pnpm add <pkg>
    • As dev dependency: pnpm add -D <pkg>
  • Run Scripts:
    • pnpm <script> (e.g., pnpm test)

Dependency Management

pnpm uses a content-addressable store and a non-flat node_modules structure. This ensures:

  • Strictness: You cannot access dependencies that are not explicitly declared in your package.json.
  • Efficiency: Disk space is saved by sharing package files across projects.
Changes

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.

  1. yesterday First seen · 28 lines · 192 tokens per session scan A 626d6ac71534

Subscribe to this mod's changes

tech-stack is a cursor rule published in the GitHub repository yu-iskw/skill-inspector (2 stars, last pushed 16d ago), licensed Apache-2.0. It adds 192 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.