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 commands/emaraschio/cursor-commands/setup-new-featuregit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/commands/emaraschio/cursor-commands/setup-new-feature)<a href="https://agentmods.dev/commands/emaraschio/cursor-commands/setup-new-feature"><img src="https://agentmods.dev/badge/commands/emaraschio/cursor-commands/setup-new-feature.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.00011 | $0.00391 |
| Opus 5 | $0.00005 | $0.00196 |
| Sonnet 5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
setup-new-feature 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 5d 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
Overview
Scaffold a new feature across layers. Full workflow: .cursor/skill-contracts/setup-new-feature/SKILL.md (user install: ~/.cursor/skill-contracts/setup-new-feature/SKILL.md).
Defaults
None. See skill for workflow defaults.
Steps
- Read
.cursor/skill-contracts/setup-new-feature/SKILL.mdfor the full agent contract; if that file is missing, read~/.cursor/skill-contracts/setup-new-feature/SKILL.md. - Execute the workflow in order; do not skip safety steps.
- Report outcomes per skill (summary, tables, or checklist as specified).
Anti-patterns
- Do not over-engineer the scaffold. Trigger: standing up the structure for a new feature. Wrong: adding layers, abstractions, or files the feature does not yet need. Correct: scaffold the minimum the feature requires and grow it as real needs appear. Reason: speculative structure is dead weight every later change has to carry.
- Match the existing project structure. Trigger: deciding where new files and modules belong. Wrong: inventing a new layout or convention beside the established one. Correct: mirror the repository's existing structure, naming, and conventions. Reason: a divergent layout fragments the codebase and slows everyone who navigates it.
Examples
/setup-new-feature
Maintainers
Behavioral eval: .cursor/skill-contracts/setup-new-feature/eval/cases.md. Ship gate sections: A before changing SKILL.md or this command.
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.
- 5d ago First seen · 38 lines · 11 tokens per session scan A 682fe25252b5
setup-new-feature is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 28d ago), licensed MIT. It adds 11 tokens to every session and 391 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 commands, from other repositories
grok_init
Discover, verify, and persist the local HTTP proxy used by Grok Build Supervisor.
analyze-deps
Analyze the project's dependency tree, identify unused or duplicate dependencies, and suggest optimizations.
code-review
Review the code changes in this conversation (or the files I've @-mentioned) systematically.
security-audit
Perform a security-focused review of the code I've @-mentioned (or the most relevant changes in this conversation).
fix-issue
Command "fix-issue" from HKTITAN/cursor-best-practices, covering steps and rules.
run-tests-and-fix
Run the project's test suite, fix any failures, and report what changed.