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-projectgit 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-project)<a href="https://agentmods.dev/skills/wilgon456/paseobility/paseo-project"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-project/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-project"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-project.svg" alt="Reviewed on agentmods" width="80" 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.00089 | $0.00619 |
| Opus 5.5 | $0.00036 | $0.00248 |
| Sonnet 5.5 | $0.00018 | $0.00124 |
| Haiku 4.5 | $0.00009 | $0.00062 |
Grade A, and why
paseo-project 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paseo Project
This combines /paseo-session-brief and /paseo-project-bootstrap. Pick the
mode from the requested outcome.
- A readable overview, commands, or a written handoff brief: brief mode.
- Initial repository setup, environment repair, skill installation, or generated context: setup mode.
Shared context
Confirm the project root and git state. Reuse the conversation's verified
context and existing .paseobility/ files after a freshness check (compare
their date with recent commits and changed manifests). Read only missing or
changed material: README, applicable agent instructions, overview/setup docs,
command manifests. Do not resurvey a repository just because a session began.
Keep .paseobility/ context current: when it is missing or stale and you have
just learned the project, write or refresh it so the next session can reuse it
instead of resurveying. It is local state; if the repository does not already
ignore .paseobility/, add it to the local exclude file resolved by
git rev-parse --git-path info/exclude rather than .gitignore; .git can be
a file in a worktree.
Generated context is a snapshot and never overrides current AGENTS.md
instructions, including nested ones for selected modules.
A Git root, monorepo package and registered Paseo workspace can differ; record which one each command targets.
Inspect Paseo runtime only when the request concerns it: paseo --version,
paseo daemon status --json, paseo project ls --json,
paseo workspace ls --json (0.12+ hides background workspaces unless
--background is added; 0.11 rejects that flag). Do not infer workspace identity from pwd alone;
aliases/symlinks may differ. If paseo script ls --cwd <path> --json reports
WORKSPACE_NOT_FOUND, resolve the existing workspace and use
--workspace <id>; do not create a duplicate record. An empty script list is
valid; never invent script names.
Never restart the Paseo daemon (other agents depend on it). Preserve unrelated changes, running work and private state. Report secrets only as redacted metadata.
What ships with it
2 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.
- yesterday Changed · +2 lines c5239c45e3c6
- 4d ago Changed · +3 lines · +22 tokens per session 6d87001e2457
- 8d ago Changed · +3 lines · +11 tokens per session 2f47e37691d6
- 15d ago Changed · +5 lines e270acfac6aa
- 1mo ago First seen · 44 lines · 56 tokens per session scan A 4ee06b4a126d
paseo-project is a skill published in the GitHub repository wilgon456/Paseobility (25 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 619 once invoked, about $0.0004 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-09-22.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.