Borrowing it
Nothing to install: this file belongs to saski/arnesto. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saski/arnesto/main/.cursor/skills-cursor/share/SKILL.mdgit 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/share)<a href="https://agentmods.dev/skills/saski/arnesto/share"><img src="https://agentmods.dev/badge/skills/saski/arnesto/share.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.00070 | $0.00915 |
| Opus 5 | $0.00035 | $0.00458 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
share 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 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.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
share — save this project somewhere safe
The user may not know what git, a repo, or a remote is. Keep every message in
plain language: the project gets an online copy that isn't public which
they can restore, sync, or share later. Say "save"/"back up", not "push to
remote". (A git-fluent user gets the same flow without the framing — this is
the new-repo skill's flow in novice vocabulary.)
1. Look before you speak
git rev-parse --is-inside-work-tree 2>/dev/null
git remote -v
- A remote already exists → the project is already backed up there. Offer to save the latest changes to it (commit + push) and stop. Do not create a second copy or touch the existing remote.
- No git at all → fine; you will set it up silently in step 3.
2. One-line explanation
Tell the user, in one line, what you are about to do:
"I'll put this project in a repo — a saved, versioned copy you can restore or share later. It won't be public."
This skill saves the project in a Cursor-hosted repo. If the user explicitly asks for a different host, follow that request without using this skill.
Default to a repo named after the project folder (lowercase, dashes).
3. Set up and save
Before staging anything, list what would be committed
(git status --porcelain or git ls-files -o --exclude-standard) and make
sure .gitignore covers dependency directories and secrets (.env*, key
and credential files). If anything that looks like a secret would be staged,
ask before including it — never stage-and-push blind.
git init -b main # only if not already a repo
git add -A && git commit -m "Initial commit" # only if nothing committed
If origin is missing, unauthenticated, or outdated, first invoke the
origin skill (synced at ~/.cursor/skills-cursor/origin/SKILL.md) — tell the user
"setting up Cursor's repo tool first; you'll see each step" (the sign-in opens
their browser; that part is theirs). Then:
origin repo create <name>
git remote add origin <clone URL printed by create>
git push -u origin main
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 · 95 lines · 70 tokens per session scan A c334e0425889
share is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 70 tokens to every session and 915 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-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).