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-spyware-checkgit 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-spyware-check)<a href="https://agentmods.dev/skills/wilgon456/paseobility/paseo-spyware-check"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-spyware-check/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-spyware-check"><img src="https://agentmods.dev/badge/skills/wilgon456/paseobility/paseo-spyware-check.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.00046 | $0.00551 |
| Opus 5.5 | $0.00018 | $0.00220 |
| Sonnet 5.5 | $0.00009 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
paseo-spyware-check 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paseo Spyware Check
Static review only: never run the target's install, build, test, lifecycle scripts, modules or binaries. That is the point of this skill. A static verdict is not a guarantee of safety.
Scan
Start with the stdlib helper (on Windows use python or py -3):
python3 <skill-dir>/scripts/spyware-check.py <github-url-or-local-path> --timeout 180
It writes a redacted JSON receipt (schema v2): source commit or local snapshot,
findings with severity, policy decision, truncation. Exit 0 means the receipt
was written, not that the repo is safe. --timeout bounds each Git call.
For deeper coverage, use the shell/PowerShell helpers and optional scanners in references/review.md. Their heuristics differ from schema v2; report them separately rather than adding counts. If a scanner is missing and the extra coverage is worth it, install it with the bundled installer and say what you installed. For confidential or offline targets, skip tools that download rules or send package inventories.
Review the evidence
- Note the exact URL/path, commit and scope. A shallow clone lacks history; a local snapshot can include uncommitted files. Check skipped, binary, generated and truncated content before trusting zero findings.
- Read the code paths that touch credentials, persistence, remote code or network sends. Docs and API-key variable names alone are not malicious; correlate with callers, triggers and destinations.
- Target-controlled scanner exclusions or config can hide findings; inspect them.
- Never verify found secrets against providers, print secret values, or upload
raw matches, logs or report directories. Cite paths, line numbers and
redacted evidence. Never run
osv-scanner fix.
Report
Verdict with evidence, the checked revision, tools that ran/failed/were missing, coverage gaps, and the next sensible step. Separate real credential material, reachable high-risk behavior, suspicious patterns and items needing manual review. A clean complete pass is "no high-risk indicators found in this static pass"; missing or truncated coverage cannot support an unqualified clean verdict. Running the target, rotating credentials or remediation are the user's call after the report.
What ships with it
9 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.
- references/review.md 11 KB
- scripts/install-scanners.ps1 2.3 KB runs code
- scripts/install-scanners.sh 2.0 KB runs code
- scripts/security_policy.py 18 KB runs code
- scripts/spyware-check-shell.test.sh 6.6 KB runs code
- scripts/spyware-check.ps1 9.4 KB runs code
- scripts/spyware-check.py 42 KB runs code
- scripts/spyware-check.sh 9.9 KB runs code
- scripts/spyware-check.test.py 13 KB runs code
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 Changed · -8 lines b5f6218eca39
- 15d ago Changed · -251 lines · -98 tokens per session scan B → A 68b2e85f2bef
- 1mo ago Changed 3fcc21e0a706
- 1mo ago First seen · 316 lines · 144 tokens per session scan B 20d431e8e470
paseo-spyware-check is a skill published in the GitHub repository wilgon456/Paseobility (25 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 551 once invoked, about $0.0002 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-08-30.
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.