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-onboardingnpx skills add ImYourBoyRoy/Portable_Web_toolkit --skill site-onboardinggit 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-onboarding)<a href="https://agentmods.dev/skills/imyourboyroy/portable_web_toolkit/site-onboarding"><img src="https://agentmods.dev/badge/skills/imyourboyroy/portable_web_toolkit/site-onboarding.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.00080 | $0.00615 |
| Opus 5 | $0.00040 | $0.00308 |
| Sonnet 5 | $0.00016 | $0.00123 |
| Haiku 4.5 | $0.00008 | $0.00061 |
Grade A, and why
site-onboarding 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Onboarding
Follow repository path docs/agent-skills/ONBOARDING_STAGES.md as the source of truth (stages S0–S9). Read that file before acting; do not invent parallel onboarding steps.
When to use
- New machine / agent environment setup
- User does not know Cloudflare well
- Creating a brand-new client site folder
- Installing Cloudflare Skills/MCP alongside the toolkit
- Guiding API token creation and
.envwiring
Rules
- Read
ONBOARDING_STAGES.mdbefore acting. - Prefer full agent control; detect sandbox limits in S0.
- Ask before host installs, Cloudflare plugin/MCP, scaffold writes, and production mutate/deploy — use the host question UI when available.
- Global PWT footprint stays light (
portable-web-toolkit-routeronly). Link heavier skills into the project with explicit--skills. - Fresh folders gaining files from
site-starteris success, not failure. - Always ask Workers vs Pages static before scaffolding.
- Verify Cloudflare tokens with
cf-agent permissions auditbefore mutations. - Re-fetch https://developers.cloudflare.com/agent-setup/prompt.md live for MCP/plugin install commands.
.envdivision of labor — copysite-starter/.env.exampleinto the client project (canonical). Do not use the toolkit-repo root.env.example(pointer only) or invent a third template:- A (user):
CLOUDFLARE_API_TOKEN,GOOGLE_PAGESPEED_API_KEY - B (agent + user): account/zone/worker or pages names, public URL — propose and challenge
- C (explain early): PostHog + GA4 — why product analytics + Google reporting matter; do not defer the conversation
- D (optional): forms/Turnstile/Instagram; registrar keys only if needed (Porkbun is an example, not required)
- A (user):
- Be curious: challenge vague names, “analytics later,” and missing required API keys before calling setup done.
- Create profiles with
init-site-profile create … --project-root .so the JSON lands in the client folder (<siteId>.site-profile.json). Never write live clients intoWeb_Toolkit/site-profiles/.
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 · 39 lines · 80 tokens per session scan A c17acfe3cf81
site-onboarding is a skill published in the GitHub repository ImYourBoyRoy/Portable_Web_toolkit (2 stars, last pushed 24d ago), licensed MIT. It adds 80 tokens to every session and 615 once invoked, about $0.0004 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
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
aws-serverless-eda
AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions,...
aws-cdk-development
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python. Use when creating CDK stacks, defining CDK constructs, implementing infrastructure as code, or when the user mentions CDK, CloudFormation, IaC, cdk synth, cdk deploy, or wants to define AWS...
aws-cost-operations
AWS cost optimization, monitoring, and operational excellence expert. Use when analyzing AWS bills, estimating costs, setting up CloudWatch alarms, querying logs, auditing CloudTrail activity, or assessing security posture. Essential when user mentions AWS costs, spending, billing,...
apify-actorization
Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.
aws-cost-cleanup
Automated cleanup of unused AWS resources to reduce costs.