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/site-readinessnpx skills add ImYourBoyRoy/Portable_Web_toolkit --skill site-readinessgit 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/site-readiness)<a href="https://agentmods.dev/skills/imyourboyroy/portable_web_toolkit/site-readiness"><img src="https://agentmods.dev/badge/skills/imyourboyroy/portable_web_toolkit/site-readiness.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.00066 | $0.00502 |
| Opus 5 | $0.00033 | $0.00251 |
| Sonnet 5 | $0.00013 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
site-readiness 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
Site Readiness
Run before material work when current readiness evidence is absent or stale.
Preflight
Resolve the active client repository, read its applicable instructions, and preserve unrelated work. Confirm the toolkit link and site profile belong to this client before running commands.
Command
node ./Web_Toolkit/site_readiness/bin/site-readiness.mjs run --project-root . --site-profile ./<name>.site-profile.json
Shortcuts: npm run readiness | npm run readiness:fix
An ordinary readiness request may write its diagnostic reports but does not
apply project fixes. Do not use readiness:fix or any mutation flag without
separate authorization for the proposed fixes.
Flags
| Flag | Effect |
|---|---|
--apply-safe-fixes |
Authorized project-init apply-safe (never overwrites) |
--install-deps |
Separately authorize dependency installation |
--build |
Run the repository-authorized build and create its artifacts |
--skip-network |
Offline/sandbox — skip integration |
Modes (auto)
sandbox | local | full (network + CF .env)
Outputs
output/site-readiness-*.json— agents read this firstoutput/site-readiness-*.md— human summary- Exit: 0 pass, 2 warn, 1 fail
Workflow
- Run readiness
- Read
nextSteps+recommendedFixesin JSON - Propose fixes; apply only the authorized set, then re-run
- Then portable-web-toolkit for deploy
- site-doctor only when site is live
Record the toolkit version as context. A newer toolkit version is a separate finding, not permission to pull source or reinstall skills. Use toolkit-update when comparison or migration is requested.
Never auto-applied
Deploy, DNS, cf-agent --apply, cache purge, registrar.
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.
- 5d ago First seen · 62 lines · 66 tokens per session scan A 2dfbf7ffdd65
site-readiness is a skill published in the GitHub repository ImYourBoyRoy/Portable_Web_toolkit (2 stars, last pushed 24d ago), licensed MIT. It adds 66 tokens to every session and 502 once invoked, about $0.0003 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-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.
architecture-decision-records
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
aria
Designs the data model, API contracts, and structural foundation of the system.
apify-competitor-intelligence
Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.