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-godgit 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-god)<a href="https://agentmods.dev/skills/wilgon456/paseobility/paseo-god"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-god/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-god"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-god.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.00070 | $0.02108 |
| Opus 5.5 | $0.00028 | $0.00843 |
| Sonnet 5.5 | $0.00014 | $0.00422 |
| Haiku 4.5 | $0.00007 | $0.00211 |
Grade A, and why
paseo-god 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paseo God
Start or resume one run
God mode is a task workflow, not extra permissions or a different model. Work autonomously inside the user's request and project instructions. Read relevant project context, not every skill, session or memory file. Load a reference below only when it helps.
-
State the goal, scope and observable acceptance criteria. Infer routine details; ask only for missing information that blocks work.
-
Create or find the run record with the installed skill's helper (Node 18+):
node <skill-dir>/scripts/god-run.mjs init --root <project-root> --goal "<goal>" node <skill-dir>/scripts/god-run.mjs list --root <project-root> node <skill-dir>/scripts/god-run.mjs resume --root <project-root> --id <run-id>Records live in
.paseobility/god/runs/<id>/; the helper only manages records. Without Node, copy RUN.md into a new uniquely named run directory. Keep these local records out of commits. -
Fill
RUN.mdwith criteria, their observable scenarios and expected check results. Keep literal paths, command names and requested formats intact. Analysis or preparation ends at the requested deliverable; do not invent implementation or runtime checks for it. Reuse the active run when the user steers the same task. To resume,listand pick the run whose goal matches; ask only if several fit. Update the- Status:line inRUN.mdyourself; the helper has no status update or completion command.
Each run has one writer. A second writer creates its own run and, when edits overlap, its own worktree. Do not rewrite another run to resolve a conflict.
Plan before substantive work
After reading enough context to choose an approach, briefly state the plan to
the user and put its TODO in RUN.md before substantive changes. For an
investigation, bug fix, change or shipping task, start the TODO from the
matching playbook. Choose
concrete actions that advance the criteria, order dependencies and include the
checks that establish the outcome. A small correction needs only one or two
steps; a larger task needs meaningful stages, not an exhaustive task graph.
Proceed without a separate plan-approval round unless a required decision is
missing. An available plan/TODO tool can show progress; keep it consistent with
the durable record rather than maintaining a different plan there.
What ships with it
11 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.
- agents/openai.yaml 43 B
- references/change-boundary.md 2.9 KB
- references/debugging.md 3.1 KB
- references/planning-and-handoff.md 5.4 KB
- references/playbooks.md 3.1 KB
- references/review.md 1.7 KB
- references/spike.md 1.9 KB
- references/verification.md 4.4 KB
- scripts/god-run.mjs 5.9 KB runs code
- scripts/god-run.test.mjs 8.0 KB runs code
- templates/RUN.md 4.3 KB
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 · +7 lines c522b2c49518
- 4d ago Changed · +67 lines a26d2d93d3c0
- 8d ago Changed · -13 lines c16bb0b3fd5d
- 9d ago Changed · +21 lines 941888ed883f
- 15d ago First seen · 92 lines · 70 tokens per session scan A a7d1d9af9082
paseo-god is a skill published in the GitHub repository wilgon456/Paseobility (25 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 2,108 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
paseo-skins
Safely browse, create, inspect, install, switch, verify, and remove themes for the Paseo desktop app. Use when a user asks an agent to change Paseo's background, build a theme from an image, apply a Paseo skin, list available themes, diagnose a theme, or restore Paseo's native appearance.
live-voice-agent
A voice-control rule for a gated Korean-and-English voice assistant. It defines which wake phrases start listening and how spoken replies must be formatted.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.