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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/wilgon456/paseobility/claude-md"><img src="https://agentmods.dev/badge/instructions/wilgon456/paseobility/claude-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.1 | $0.00542 | $0.00542 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
Paseobility CLAUDE.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 5d 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.
What it actually says
Paseobility Claude Install Guide
This repository is an AI-installable skill package. When the user gives this
repository URL and asks to install paseo-share, share Paseo artifacts, enable
cross-computer/mobile file viewing, install the requested skill instead of
merely describing the repository.
Read AGENTS.md for the complete safety and platform rules. For the common
paseo-share request, use this fast path:
-
Clone or use the provided checkout and confirm
skills/paseo-share/SKILL.mdexists. -
Detect the operating system.
-
Run the matching single-skill installer with Claude support:
./scripts/paseobility-init.sh --skill paseo-share --with-claude --no-context.\scripts\paseobility-install.ps1 -Skill paseo-share -WithClaude -
Preserve the installer's backup path if it replaced an existing copy.
-
Verify both installed copies contain
SKILL.mdandscripts/paseo-share.js:- Paseo/Codex:
~/.agents/skills/paseo-share - Claude Code:
~/.claude/skills/paseo-share - On Windows, resolve both paths under
%USERPROFILE%.
- Paseo/Codex:
-
If Node.js is available, run the installed
paseo-share.test.jsonce. -
Do not restart the Paseo daemon. Tell the user to start a new agent session or reload integrations.
The Paseobility URL is only the skill source. Never configure this repository
as the artifact destination. Installation must remain side-effect free. On the
first actual share request, run status and then onboard when unconfigured.
If GitHub CLI is missing or unauthenticated, ask the user to install gh or run
gh auth login --hostname github.com. Onboarding targets the authenticated
account’s private <login>/paseo_share repository. Create it when absent;
reuse it only when empty or already recognized as Paseo Share. Refuse public,
unrelated, or incompletely inspected same-name repositories. Use explicit
setup <repo-url> for Forgejo or another custom remote.
After installation, give the user this first-use prompt:
/paseo-share 이 파일을 공유해줘.
GitHub 연결이 필요하면 먼저 알려주고, 연결되어 있으면 내 계정의
private paseo_share 저장소를 안전하게 준비해서 사용해줘.
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.
- 5d ago First seen · 51 lines · 542 tokens per session scan A fd6fb74add1f
Paseobility CLAUDE.md is an instructions file published in the GitHub repository wilgon456/Paseobility (19 stars, last pushed 9d ago), licensed MIT. It adds 542 tokens to every session, about $0.0027 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
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.
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).