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 skills/omnigent-ai/omnigent/cursor-sdk-e2e-devnpx skills add omnigent-ai/omnigent --skill cursor-sdk-e2e-devgit clone --depth 1 https://github.com/omnigent-ai/omnigentWhat 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.00083 | $0.02350 |
| Opus 5 | $0.00042 | $0.01175 |
| Sonnet 5 | $0.00017 | $0.00470 |
| Haiku 4.5 | $0.00008 | $0.00235 |
Grade C, and why
cursor-sdk-e2e-dev scanned grade C 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/cursor-dev # remove scratch bundles How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor SDK harness: end-to-end dev & testing
The cursor harness drives the Cursor Python SDK (cursor_sdk, an
AsyncAgent over a local bridge) and bridges Omnigent's sys_* tools into
Cursor as SDK custom_tools. This skill is the proven recipe for running it
for real against a live local server — not just the unit tests.
The harness runs as a local runner from your current checkout, so
omni run <bundle> --server <url>exercises exactly the code you're on.
Prerequisites (check these first)
- You're on the branch you want to test. The cursor harness merged to
main(#203/#204). Test onmainunless validating a specific branch. - A Cursor API key is configured. The SDK requires an API key
(
crsr_…); there is nocursor-agent loginpath. Verify (booleans only — never print the key):
If both are.venv/bin/python -c "from omnigent.onboarding.cursor_auth import cursor_api_key_configured; import os; print('config:', cursor_api_key_configured(), 'env:', bool(os.environ.get('CURSOR_API_KEY')))"False, runomni setupand register a Cursor key, orexport CURSOR_API_KEY=crsr_…. cursor-sdkis installed (a baseline dependency):.venv/bin/python -c "import cursor_sdk; print(cursor_sdk.__file__)".- Network egress to Cursor's backend. The bridge subprocess talks to Cursor's own API; a turn that hangs or fails to connect on a locked-down host is usually an egress problem, not a harness bug.
Step 1 — start a local server
cd /path/to/omnigent
.venv/bin/omni server --background # spawns a detached server on a free loopback port
.venv/bin/omni server status # prints the URL, e.g. http://127.0.0.1:6767
Use the printed URL below as $SERVER. (You can also run a foreground
server on a fixed port with omnigent server --port 7777 --no-open.)
Step 2 — build a cursor agent bundle
A spec with spec_version must be a directory containing config.yaml —
not a single .yaml file. Minimal cursor agent:
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.
- 3d ago First seen · 177 lines · 83 tokens per session scan C 39ae0c2932a8
cursor-sdk-e2e-dev is a skill published in the GitHub repository omnigent-ai/omnigent (9,591 stars, last pushed yesterday), licensed Apache-2.0. It adds 83 tokens to every session and 2,350 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-production-validator
Agent skill for production-validator - invoke with $agent-production-validator.
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…