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.00133 | $0.01692 |
| Opus 5 | $0.00067 | $0.00846 |
| Sonnet 5 | $0.00027 | $0.00338 |
| Haiku 4.5 | $0.00013 | $0.00169 |
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 8d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paseo Share
Use a dedicated private Git repository as a small artifact inbox. Run the
bundled Node.js CLI for deterministic Git operations. It uses only local
git fetch/rebase/commit/push; it never creates or runs GitHub Actions.
This feature is intentionally independent of Paseo's daemon, MCP tool names, agent profiles, and workspace lifecycle. Paseo 0.6 compatibility depends only on the skill being installed and discovered; sharing continues through the bundled CLI.
Requirements
- Require
nodeandgiton every computer. - Require GitHub CLI (
gh) for automatic GitHub onboarding. Keep explicitsetup <repo-url>support for Forgejo or another dedicated remote. - Use one dedicated private repository for all computers.
- Use one repository per person or fully trusted device group. Do not treat it as a multi-tenant exchange for mutually untrusted collaborators.
- Let automatic onboarding configure local Git authentication through
gh. For custom remotes, use SSH or the operating system credential manager. Never put a token in the repository URL. - Expect mobile viewers to be signed in to the Git host for private links.
The CLI stores machine-local configuration and its clone under
~/.paseo/share/ by default. Override this only for testing with
PASEO_SHARE_HOME.
Command runner
Resolve this skill's installed directory and run:
node <skill-dir>/scripts/paseo-share.js <command> [arguments]
Commands:
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 <directory>] [--force]
status
Add --json to publish, list, latest, fetch, or status when
machine-readable output helps.
First-time setup
- Run
statusfirst. - Treat the user’s first actual Paseo Share request as authorization to run
onboard; installation alone must remain side-effect free. - If
ghis missing or unauthenticated, ask the user to install it or rungh auth login --hostname github.com, then retry. GitHub Connector access alone does not prove that localgit pushis authenticated. - Let
onboardconfigure local Git authentication, resolve the authenticated login, and target<login>/paseo_sharewith private visibility. - Create the repository when absent. Reuse it only when it is private and either empty or already contains a recognized Paseo Share artifact tree.
- Refuse automatic setup when the fixed-name repository is public, contains unrelated data, cannot be completely inspected, or local Git authentication fails. Never change visibility, rename, delete, or overwrite repository contents automatically.
- For Forgejo or a user-selected custom repository, obtain its URL and run
setup <repo-url>instead ofonboard. - Let the CLI infer the machine name unless the user wants a stable friendly
name such as
macbook,desktop, orlaptop. Report the repository, machine name, branch, and checkout path without exposing credentials.
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.
- 8d ago First seen · 167 lines · 133 tokens per session scan A 92ff9d506338
paseo-share is a skill published in the GitHub repository wilgon456/Paseobility (19 stars, last pushed 13d ago), licensed MIT. It adds 133 tokens to every session and 1,692 once invoked, about $0.0007 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 skills, from other repositories
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
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.
contributor
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they…
git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…