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 saski/arnesto --skill origingit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/origin)<a href="https://agentmods.dev/skills/saski/arnesto/origin"><img src="https://agentmods.dev/badge/skills/saski/arnesto/origin.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.1 | $0.00062 | $0.00915 |
| Opus 5 | $0.00031 | $0.00458 |
| Sonnet 5 | $0.00012 | $0.00183 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade C, and why
origin scanned grade C with 2 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 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://downloads.cursor.com/origin/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://downloads.cursor.com/origin/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
origin — set up and repair the origin CLI
Cursor hosts git repositories at origin.cursor.com. The origin CLI
manages them. This skill covers getting the CLI working and recovering from
its common failure states. It does not decide whether to use Cursor-hosted
repos — workflow skills and the user do that.
Platform check first
Supported: macOS and Linux (including WSL). On native Windows (outside WSL), Origin repo operations are not supported yet — say so plainly. Do not improvise a Windows install.
1. Detect the current state
command -v origin || { test -x ~/.local/bin/origin && echo ~/.local/bin/origin; }
origin auth status
- Binary missing → install (step 2), then authenticate (step 3).
- Binary present but
auth statusshows no session → authenticate (step 3). - Both fine → nothing to set up; continue with whatever you were doing.
If origin is not on PATH but ~/.local/bin/origin exists, invoke it by
that absolute path.
2. Install
curl -fsSL https://downloads.cursor.com/origin/install.sh | sh
The installer verifies the download's checksum and symlinks
~/.local/bin/origin. New shells may not have ~/.local/bin on PATH yet —
use the absolute path for the rest of the session.
3. Authenticate
origin auth login
This opens the user's browser (the same Cursor login they already have — one
click for most users) and configures the git credential helper for
origin.cursor.com, so git push/git pull work afterwards with no extra
setup. Wait for the command to complete.
- Headless or SSH session: the CLI prints a login URL instead of opening a browser. Show the user that URL and wait.
- Never ask the user to paste tokens into chat, and never print credentials. The CLI stores them in the OS keychain / its credentials file.
4. Recover from known failures
| Failure signature | Fix |
|---|---|
origin: command not found |
Install (step 2). |
Authentication failed for 'https://origin.cursor.com/...' on git push/pull |
origin auth status, then origin auth login, then retry the git command. |
No Origin namespace for the account (origin repo create / repo list errors mentioning a missing namespace) |
Relay the error's own guidance in plain language. For a user on a team, a team admin sets the namespace up at cursor.com/codebase. Do not retry in this session. |
| Not authorized to access a namespace | The user's team has Origin, but this account lacks repo access there — a team admin can grant it. |
origin auth login never completes |
The user has not finished the browser step. Ask them to complete it or re-run the command; do not work around it. |
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 · 93 lines · 62 tokens per session scan C bbdbd1ecef63
origin is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 62 tokens to every session and 915 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
git-ai-search
Search and restore AI conversation context from git history.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
machinist
Use Machinist to create, assign, monitor, and resume software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, lifecycle labels, direct runs, or managed queue.
repo-sentinel
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).