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.
git clone --depth 1 https://github.com/terrylica/cc-skillsWrote 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/plugins/terrylica/cc-skills/web-forge)<a href="https://agentmods.dev/plugins/terrylica/cc-skills/web-forge"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/web-forge.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
web-forge 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.
What it actually says
{
"name": "web-forge",
"description": "Supervised dashboard automation for API-less operations - persistent-profile CDP harness, secrets-safe token/OAuth-app forging, declarative Cloudflare Access walls (GitHub SSO + email OTP) that work directly on *.workers.dev",
"version": "30.3.0",
"source": "./plugins/web-forge",
"category": "devops",
"author": {
"name": "Terry Li",
"url": "https://github.com/terrylica"
},
"keywords": [
"browser-automation",
"cdp",
"playwright",
"cloudflare-access",
"zero-trust",
"oauth-app",
"api-token",
"secrets",
"vault",
"workers",
"sso",
"otp"
],
"strict": false
}What ships with it
3 files beside marketplace.json#web-forge 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.
- today Changed 238d88cd31f1
- 2d ago First seen · 26 lines scan A addbbbe4e2b3
web-forge is a plugin published in the GitHub repository terrylica/cc-skills (62 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-05.
Other plugins, from other repositories
homelab-ops
High-level operational runbooks for homelab management: DR-node power management, DNS ingress convergence, secrets-engine identity bring-up, Proxmox VE cluster operations, Terrakube operations, PXE netboot installs, LLM router operations, workstation off-box backup, Dell iDRAC BMC operations, and resumable ZFS…
infra-orchestration
Cross-repo infrastructure orchestration for Terraform and Ansible workflows.
infra-standards
Infrastructure standards for Proxmox, Terraform, Ansible: VMID/IP assignment ranges and the Terraform-to-Ansible inventory contract.
cloudflare-connect
Adds a subdomain to a Cloudflare-managed zone and wires it to a hosting platform (Railway, Vercel, more) via browser automation. Handles both sides end-to-end: platform-side custom domain attach AND Cloudflare DNS record creation. No CLI or API token required.
gcp-setup
Automates Google Cloud Console setup via browser. Walks through project creation, API enabling, service accounts, IAM, billing, OAuth, Cloud Run, and firewall config — click by click. Auto-detects requirements from your codebase when invoked mid-feature.
gtm-workflow
Drives Google Tag Manager via browser automation: inspect containers, verify events fire correctly, add/edit tags and triggers, preview and publish versions safely. Uses chrome-devtools-mcp, never handles credentials.