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/athola/skrills/sync-from-cursorgit clone --depth 1 https://github.com/athola/skrillsWrote 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/athola/skrills/sync-from-cursor)<a href="https://agentmods.dev/commands/athola/skrills/sync-from-cursor"><img src="https://agentmods.dev/badge/commands/athola/skrills/sync-from-cursor.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.00026 | $0.00364 |
| Opus 5 | $0.00013 | $0.00182 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
sync-from-cursor 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
Sync from Cursor
Sync from Cursor IDE using the skrills MCP server.
Use the mcp__plugin_skrills_skrills__sync-from-cursor tool with:
to: Target agent (claude, codex, or copilot). Default: claudedry_run: Preview changes without writing
Parse $ARGUMENTS for:
--to <agent>or-t <agent>: Target agent (default: claude)--dry-runor-n: Preview mode
This reads from ~/.cursor/:
- Skills from
.cursor/skills/{name}/SKILL.md - Commands from
.cursor/commands/{name}.md - Agents from
.cursor/agents/{name}.md(field translation: is_background→background) - Hooks from
.cursor/hooks.json(event names: camelCase→PascalCase) - Rules from
.cursor/rules/*.mdc(alwaysApply→CLAUDE.md, globs preserved) - MCP from
.cursor/mcp.json
Report:
- Artifacts synced per type
- Cursor-only hook events (afterFileEdit, beforeShellExecution) preserved in raw content
- Files created/updated in target directory
Handle errors:
- If Cursor directory doesn't exist: Report and exit cleanly
- If target invalid: List valid options (claude, codex, copilot)
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 · 35 lines · 26 tokens per session scan A 084adf6c5140
sync-from-cursor is a command published in the GitHub repository athola/skrills (69 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 364 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-30.
Other commands, from other repositories
browser
Inspect and control the current AO session's target-isolated browser. The desktop app must be open. The agent and user share the same live page, cookies, navigation state, and WebContentsView; the runtime remains usable while the Browser panel is hidden. Tabs in this worker share an ephemeral browser profile, while…
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
spawn
Spawn a worker agent session in a registered project. The session runs the chosen agent in a fresh git worktree. Register the project first with ao project add.
review
Manage AO code reviews of a worker's PR.
import
Import reads the legacy Agent Orchestrator flat-file store (/.agent-orchestrator) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before…
learn-workspace-intent
Run Contorium BYOK workspace intent learning when API keys are configured.