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 wilgon456/Paseobility --skill paseo-sharegit clone --depth 1 https://github.com/wilgon456/PaseobilityWrote 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/wilgon456/paseobility/paseo-share)<a href="https://agentmods.dev/skills/wilgon456/paseobility/paseo-share"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-share/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/wilgon456/paseobility/paseo-share"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-share.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00117 | $0.01356 |
| Opus 5.5 | $0.00047 | $0.00542 |
| Sonnet 5.5 | $0.00023 | $0.00271 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
paseo-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 today.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paseo Share
A dedicated private Git repository is the user's file inbox across computers
and phone. The bundled Node.js CLI does all Git work with plain
fetch/rebase/commit/push; no daemon, no GitHub Actions, and no
dependency on Paseo's daemon or MCP tools.
Needs node and git on every computer, and GitHub CLI (gh) for automatic
onboarding. Custom remotes (Forgejo etc.) use setup <repo-url> with SSH or
the OS credential manager; never put a token in the URL. Use one repository
per person or fully trusted device group. State and the clone live under
~/.paseo/share/ (PASEO_SHARE_HOME overrides, for tests).
Commands
node <skill-dir>/scripts/paseo-share.js <command> [arguments]
onboard [--machine <name>] [--branch <name>]
setup <repo-url> [--machine <name>] [--branch <name>]
publish <file...> [--note <text>]
list [--limit <number>]
latest
fetch <artifact-id|latest> [--output <path>] [--force]
status
--json works on onboard, setup, publish, list, latest, fetch and status.
First use
Installation stays side-effect free; the first real share request authorizes onboarding.
- Run
status; if unconfigured, runonboard. - If
ghis missing or unauthenticated, ask the user to install it or rungh auth login --hostname github.com, then retry. A GitHub connector alone does not prove localgit pushworks. onboardsets up Git auth throughghand targets<login>/paseo_shareas a private repository. It creates it when absent and reuses it only when it is private and empty or already a Paseo Share tree. It refuses a public, unrelated, or incompletely inspected same-name repository, and never changes visibility, renames, deletes, or overwrites one. Relay that refusal and offersetup <repo-url>with another private repository.- Report repository, machine name, branch and checkout path. Each computer
runs the same onboarding; the CLI infers the machine name unless the user
wants a friendly one (
--machine macbook).
What ships with it
3 files 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.
- today Changed · -2 lines · -25 tokens per session c45b6fe55728
- yesterday Changed · +8 lines 6907ea10e3fc
- 4d ago Changed · -3 tokens per session 17e7f886bf7d
- 8d ago Changed · -61 lines · +12 tokens per session b5997df9a1ac
- 15d ago Changed · +6 lines 59b39ba070d6
- 1mo ago Changed 1cc635cf5ed9
- 1mo ago First seen · 167 lines · 133 tokens per session scan A 92ff9d506338
paseo-share is a skill published in the GitHub repository wilgon456/Paseobility (25 stars, last pushed today), licensed MIT. It adds 117 tokens to every session and 1,356 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
Dotfiles
Manage /.zshrc and a chosen set of /.config/ directories (you name them in Config.md) against a private GitHub dotfiles repo. Intents: Push (verify private remote, scan secrets), Pull (clone/diff), Sync, Restore (timestamped backup), Status, Backup (local timestamped copy). Security scan blocks .env, secrets, tokens…
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…
git-guardrails-claude-code
A Claude Code setup that blocks selected destructive Git commands before they run. Git is a tool for tracking code changes; the blocked commands include pushing, deleting branches, discarding changes, and hard resets.