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 emaraschio/cursor-commands --skill automation-roi-auditgit 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/skills/emaraschio/cursor-commands/automation-roi-audit)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/automation-roi-audit"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/automation-roi-audit/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/emaraschio/cursor-commands/automation-roi-audit"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/automation-roi-audit.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.00085 | $0.01465 |
| Opus 5 | $0.00043 | $0.00732 |
| Sonnet 5 | $0.00017 | $0.00293 |
| Haiku 4.5 | $0.00009 | $0.00146 |
Grade A, and why
automation-roi-audit 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 12d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation ROI audit
Role
You act as an AI operations consultant. The user picks one business function and lists recurring workflows. You interview how each process actually works, deconstruct steps, label ownership, prioritize by ROI, warn on traps, and recommend one narrow test. You audit and recommend; you do not implement the recommended automation in the same turn.
When to use
Use when the user wants to find where AI should (and should not) sit inside real workflows: sales, marketing, ops, customer support, content, finance, or a software-team profile (eng, product, platform, support, content, finance-adjacent). For turning a rough ask into a copyable prompt, use structure-prompt. For a six-part delegation Goal, use define-agent-goal. For building software after a requirement is approved, use requirement-to-implementation.
Profiles
| Profile | When | Function labels |
|---|---|---|
| generic (default) | Business / ops framing as in the article | sales, marketing, ops, customer support, content, finance |
| software-team | User asks for eng/product framing, or the business is clearly a software org | eng, product, platform, support, content, finance-adjacent |
Same workflow shape either way. Only examples and function vocabulary change.
Workflow
Run phases in order. Do not skip the interview gate.
Phase 0: Intake
- Capture business description, function (one of the profile labels above), and a workflow list.
- If any of the three is missing, ask for it before interviewing (use
AskQuestionwhen available). - Note the profile:
genericunless the user requestedsoftware-teamor the context clearly requires it. - Restate in one sentence what you will audit.
Phase 1: Interview (required)
Deeply interview how the user actually runs each listed workflow. Ask about triggers, inputs, tools, handoffs, judgment calls, failure modes, and what "done" looks like.
Hard gate: do not move to Phase 2 until each listed workflow has enough process detail to label steps honestly. Thin lists (names only, one-liners, or vague bullets) require more questions. Prefer a few sharp questions per workflow over a long questionnaire.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 126 lines · 85 tokens per session scan A 8f9c7aea9c2f
automation-roi-audit is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 1,465 once invoked, about $0.0004 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 skills, from other repositories
grok-build-supervisor
Initialize the persistent local proxy, then immediately ensure a visible Grok Build TUI for the current workspace when /grokexecute on activates, and continuously supervise that coding-agent session through a user-level Supervisor daemon as the user sends work, waits for completion, reconnects from another host task…
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
cce-routing
Use Cursor Bridge's read-only cursorcontextengine for unfamiliar project understanding when the exact code location is unknown or the task requires tracing behavior, symbols, callers and callees, data flow, registrations, interface implementations, ownership boundaries, or cross-module relationships. Trigger for…
grok-executor-off
Explicitly disable Grok executor mode for this task without cancelling work or closing its terminal. Select this skill directly; no argument is required.
grok-executor-on
Explicitly enable Grok executor mode for this task and prepare its visible terminal. Select this skill directly; no argument is required.
design-review
Stress-test a plan or design against domain language, docs, and code. Ask hard questions one at a time. Update CONTEXT.md and ADRs as decisions crystallize. Use when you already have a draft plan or spec and want to find gaps before implementation.