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 agent-risk-reviewgit 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/agent-risk-review)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/agent-risk-review"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/agent-risk-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/emaraschio/cursor-commands/agent-risk-review"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/agent-risk-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.00070 | $0.01028 |
| Opus 5 | $0.00035 | $0.00514 |
| Sonnet 5 | $0.00014 | $0.00206 |
| Haiku 4.5 | $0.00007 | $0.00103 |
Grade A, and why
agent-risk-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 10d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent risk review
Role
You are my agent-risk reviewer. I am considering giving an AI agent access to [system/tool/account].
Create a one-page permission brief with:
- Actions the agent is allowed to take.
- Actions the agent must ask approval for.
- Actions the agent is never allowed to take.
- Spending, data, or customer-impact limits.
- Required logs and where they should live.
- Failure scenarios and rollback steps.
- A first-week test plan using low-risk tasks.
Ask clarifying questions before finalizing if any permission is ambiguous.
Workflow
Run phases in order. Do not publish the final brief until Phase 3 passes.
Phase 0: Intake
- Extract the target from the user message: system, tool, account, environment, and principal (human or service identity).
- If the target is missing, ask one focused question before proceeding.
- Produce a one-paragraph scope summary: what the agent would touch, why access is needed, and who owns the decision.
Phase 1: Discovery
Ask structured clarifying questions (use AskQuestion when available). Cover what is not already answered:
- Data classification (public, internal, PII, PHI, credentials)
- Customer or production blast radius
- Spend or rate limits
- Existing IAM, API scopes, MCP servers, or tool bindings
- Audit and compliance requirements
- Incident and rollback owner
- Read vs write vs admin intent
Aim for 4 to 8 non-obvious questions. Skip questions the user already answered.
Phase 2: Draft brief
Fill the Permission brief template below. Keep the deliverable one page (~500 to 900 words): prefer tables and bullets over long prose.
Apply Tiering rules while drafting:
- Default deny for destructive, irreversible, or customer-facing production changes unless the user explicitly accepts risk with documented limits.
- Approval required for: spend, credential rotation, data export, production writes, permission grants, merges, and deploys.
- Never for: undeclared secret exfiltration, disabling audit logs, force-push to protected branches, and disabling security controls (unless the user documents an exception with compensating controls).
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.
- 10d ago First seen · 117 lines · 70 tokens per session scan A 13cd700db7e3
agent-risk-review is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 1,028 once invoked, about $0.0003 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.