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/adobedocs/ff-services-docs/security-lang-nodegit clone --depth 1 https://github.com/AdobeDocs/ff-services-docsWhat 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.00564 | $0.00564 |
| Opus 5 | $0.00282 | $0.00282 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
security-lang-node scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Rule:** Never use `req.body`, `req.query`, or similar inputs directly in `fs`, `child_process`, or system-level calls. This is a copy
100% identical to secure-dev-node — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: globs: /*.tsx,/.ts,**/.js alwaysApply: false
Secure Node.js Development
These rules apply to all Node.js code in the repository and aim to prevent common security risks through disciplined use of input validation, output encoding, and safe APIs.
All violations must include a clear explanation of which rule was triggered and why, to help developers understand and fix the issue effectively.
Generated code must not violate these rules. If a rule is violated, a comment must be added explaining the issue and suggesting a correction.
1. Do Not Use User Input in File Paths or Commands
- Rule: Never use
req.body,req.query, or similar inputs directly infs,child_process, or system-level calls.
2. Avoid eval, Function, and vm on Dynamic Input
- Rule: Do not use
eval(),new Function(), orvm.runInNewContext()with user-controllable values.
3. Avoid Synchronous child_process and Shell Execution
- Rule: Do not use
execSync,spawnSync, or shell execution functions with untrusted input. Avoid them unless strictly necessary and audited.
4. Use Environment Variables for Secrets
- Rule: Never hardcode secrets such as API Keys, private keys or credentials. Use environment variables and secure configuration loading.
5. Sanitize and Validate All External Input
- Rule: All inputs (query params, request bodies, headers) must be validated and sanitized before use in logic, queries, or file access.
6. Escape Output for HTML or CLI
- Rule: Escape dynamic output when inserting into HTML, Markdown, or command-line interfaces to prevent injection.
7. Avoid Insecure HTTP Libraries or Defaults
- Rule: Always use HTTPS for remote calls. Do not disable SSL validation or use
httpin production environments.
8. Keep Dependencies Updated and Scanned
- Rule: Regularly audit dependencies using
npm audit,yarn audit, or tools like Snyk. Avoid packages that are deprecated or unmaintained.
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 · 45 lines · 564 tokens per session scan A 9019cc2470bb
security-lang-node is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 564 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). It is 100% identical to secure-dev-node, differing in 0 lines, and is treated as a copy.
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.