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 instructions/wilgon456/paseobility/agents-mdgit 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/instructions/wilgon456/paseobility/agents-md)<a href="https://agentmods.dev/instructions/wilgon456/paseobility/agents-md"><img src="https://agentmods.dev/badge/instructions/wilgon456/paseobility/agents-md.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.01699 | $0.01699 |
| Opus 5 | $0.00849 | $0.00849 |
| Sonnet 5 | $0.00340 | $0.00340 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
Paseobility AGENTS.md 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 4d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paseobility Agent Install Guide
Use this file when a user gives you this repository URL and asks you to install or set up Paseobility for their local Paseo environment.
This repository is designed for an AI-agent install flow: the user gives Codex, Claude, or a Paseo agent the GitHub URL, and the agent reads this file before copying the bundled skills into the local skill directory.
Paseo Share fast path
If the user gives this repository URL and asks to install paseo-share, share
files between Paseo computers, or enable mobile artifact viewing, proceed with
the single-skill installation without asking them to choose among the bundled
skills.
Do not confuse the two repositories involved:
- This Paseobility repository is the skill source used for installation.
- The user's separate private repository is the artifact repository used
later by
paseo-share.
Installing the skill does not create the artifact repository. On the first
actual share request, run status; when unconfigured, use onboard. If GitHub
CLI is missing or unauthenticated, ask the user to install gh or run
gh auth login --hostname github.com. After authentication, onboarding must
target the authenticated account’s private <login>/paseo_share repository,
creating it when absent or reusing it only when empty or already recognized as
a Paseo Share repository. Refuse public, unrelated, or incompletely inspected
same-name repositories. Use explicit setup <repo-url> for Forgejo or a custom
remote.
Use the convenience installer so an existing installation is backed up:
./scripts/paseobility-init.sh --skill paseo-share --no-context
On Windows PowerShell:
.\scripts\paseobility-install.ps1 -Skill paseo-share
When running under Claude Code or when the user requests Claude support, also install the same skill into the Claude directory:
./scripts/paseobility-init.sh --skill paseo-share --with-claude --no-context
.\scripts\paseobility-install.ps1 -Skill paseo-share -WithClaude
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.
- 4d ago First seen · 201 lines · 1,699 tokens per session scan A c86628b4a565
Paseobility AGENTS.md is an instructions file published in the GitHub repository wilgon456/Paseobility (19 stars, last pushed 8d ago), licensed MIT. It adds 1,699 tokens to every session, about $0.0085 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.