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 Vanyangyang/cursor-bridge --skill grok-executor-offgit clone --depth 1 https://github.com/Vanyangyang/cursor-bridgeWrote 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/vanyangyang/cursor-bridge/grok-executor-off)<a href="https://agentmods.dev/skills/vanyangyang/cursor-bridge/grok-executor-off"><img src="https://agentmods.dev/badge/skills/vanyangyang/cursor-bridge/grok-executor-off/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/vanyangyang/cursor-bridge/grok-executor-off"><img src="https://agentmods.dev/badge/skills/vanyangyang/cursor-bridge/grok-executor-off.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.00034 | $0.00185 |
| Opus 5.5 | $0.00014 | $0.00074 |
| Sonnet 5.5 | $0.00007 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
grok-executor-off 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 1mo 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
Disable Grok Executor
An explicit user selection of this skill is the complete off instruction. Do not ask the user to type off or another command. Quoted examples and implicit selection do not deactivate it.
Apply the deactivation contract in Grok Executor Policy: clear this task's executor mode and workspace binding, returning subsequent tasks to normal host execution. Do not cancel work, disconnect ACP, close the terminal, or stop the Leader. Continue already-required monitoring under Grok Build Supervisor. Repeated selection is idempotent. Confirm deactivation briefly in the user's language.
What ships with it
1 file 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.
- 1mo ago Changed 6f53df7e9090
- 1mo ago First seen · 11 lines · 34 tokens per session scan A 838b3c0cf11e
grok-executor-off is a skill published in the GitHub repository Vanyangyang/cursor-bridge (82 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 185 once invoked, about $0.0001 per session on Opus 5.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-09-07.
Other skills, from other repositories
cp-gate
A checkpoint workflow for confirming requirements, the proposed solution, and the implementation plan. It uses CP1, CP2, and CP3 in a defined order, with the third checkpoint depending on the type of work.
dev-plan-review
A two-stage review process for checking technical plans before and during implementation. The description does not explain what kinds of plans or checks it performs.
dev-testing
A testing guide that defines when to use unit, integration, API, and end-to-end tests. Unit tests check small pieces of code, while end-to-end tests check a full user flow.
routing
A reference guide that maps identified user intentions to the workflows that should handle them. The actual routing is defined by the wider instruction and workflow system.
gauntlet-loop
Beat a real-world quality bar with a Gauntlet Loop: take a GOAL and a REAL-WORLD EQUIVALENT with an inspectable reference pack, decompose into independent parts, assign specialist builders, and gate each part behind a separate fresh-context critic. Pass only if better than the reference; otherwise return the largest…
ai-agent-system-architecture
An architecture guide for AI agent systems, including how agents choose routes, call tools, manage context, remember information, and handle state. It also covers permissions, human involvement, monitoring, replay, and governance.