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 skills/imyourboyroy/portable_web_toolkit/toolkit-updatenpx skills add ImYourBoyRoy/Portable_Web_toolkit --skill toolkit-updategit clone --depth 1 https://github.com/ImYourBoyRoy/Portable_Web_toolkitWrote 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/imyourboyroy/portable_web_toolkit/toolkit-update)<a href="https://agentmods.dev/skills/imyourboyroy/portable_web_toolkit/toolkit-update"><img src="https://agentmods.dev/badge/skills/imyourboyroy/portable_web_toolkit/toolkit-update.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.00071 | $0.00777 |
| Opus 5 | $0.00036 | $0.00388 |
| Sonnet 5 | $0.00014 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade C, and why
toolkit-update scanned grade C with 2 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. Purge legacy heavy web skills (`instagram-clone`, `portable-web-toolkit`, `site-readiness`, `site-starter`, `toolkit-update`, `vectorize-pipeline`) from global home skill directories (`~/.gemini/config/skills/`, `~/.c Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
description: Compare, plan, or apply an explicitly authorized Portable Web Toolkit or toolkit-skill update. Use when asked to check toolkit freshness, reconcile a local export with GitHub, inspect installed skill version How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Toolkit Update
Establish current state before choosing an update.
Preflight
Resolve the active repository and applicable instructions, preserve unrelated work, then locate the actual toolkit source and selected client skill roots.
Inspect
- Resolve the toolkit root and determine whether it is a real Git worktree, an export, a cache, or a linked client copy.
- Read
VERSION, package versions,skill-pack.json, Git status, current commit and remote, when available. - Inspect the selected upstream release, tag, or immutable commit.
- Compare skill directories, versions, hashes, toolkit modules, templates, instructions, and release notes.
- Classify local-only, upstream-only, modified, generated, and ignored content.
- Report the status and stop unless an update was explicitly authorized.
Before reporting a Git remote, remove URL userinfo, credentials, query strings, and fragments. Describe private-fork locations generically unless the exact locator is necessary and authorized.
Use the optional status helper only as an aid:
node ./scripts/check-agent-skills.mjs --agent <client> --scope <user-or-project>
It must not be required for an agent-driven installation.
Plan
Prefer an upstream-backed Git worktree. For an exported local folder:
- create a recoverable backup
- clone the selected upstream source into staging
- port reviewed local-only capabilities without dependencies or caches
- resolve instruction and manifest changes
- validate in staging
- switch the active path only after review
Never claim that git pull updated an export without .git.
Apply
Require exact update authorization. Use git pull --ff-only only when the
worktree and branch permit it. Otherwise use a staging clone and explicit
reconciliation.
Do not:
- run an unaudited remote installer
- overwrite unmanaged or locally modified skills
- reinstall every client as a side effect
- delete a local-only module merely because upstream lacks it
- install host software, push, tag, publish, or deploy without separate approval
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.
- 3d ago First seen · 86 lines · 71 tokens per session scan C 0119f9c2d611
toolkit-update is a skill published in the GitHub repository ImYourBoyRoy/Portable_Web_toolkit (2 stars, last pushed 22d ago), licensed MIT. It adds 71 tokens to every session and 777 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
accounting-workflow
End-to-end Malaysian accounting engagement workflow. Takes a client folder and produces accrual-basis financial statements (Excel working papers + PDF) compliant with MPERS / MFRS / ITA 1967. Covers Sole Proprietor, Partnership, Sdn Bhd, Berhad, and NGO. USE THIS SKILL when the user wants to: Start or continue an…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
aria
Designs the data model, API contracts, and structural foundation of the system.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.