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/a8cteam51/claude-code-plugins/site-from-hostnpx skills add a8cteam51/claude-code-plugins --skill site-from-hostgit clone --depth 1 https://github.com/a8cteam51/claude-code-pluginsWrote 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/a8cteam51/claude-code-plugins/site-from-host)<a href="https://agentmods.dev/skills/a8cteam51/claude-code-plugins/site-from-host"><img src="https://agentmods.dev/badge/skills/a8cteam51/claude-code-plugins/site-from-host.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.00183 | $0.03292 |
| Opus 5 | $0.00092 | $0.01646 |
| Sonnet 5 | $0.00037 | $0.00658 |
| Haiku 4.5 | $0.00018 | $0.00329 |
Grade A, and why
site-from-host scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
for c in studio team51 git curl tar jq; do command -v "$c" >/dev/null 2>&1 || echo "MISSING: $c"; done How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Studio site from a hosted Pressable / WPCOM site
Builds a local mirror of a hosted site: <siteurl>.local, wp-content = the repo,
plugins pulled off the live host, and (optionally) media served from that same host.
Scripts live in ${CLAUDE_PLUGIN_ROOT}/scripts/, alongside scaffold.sh. Delegate
every filesystem mutation, team51 call and Studio call to them — never re-implement a
step inline; that is what makes the workflow repeatable.
Step 0 — collect inputs
From the user's message, extract:
- Site — a numeric Pressable/WPCOM site ID, or a domain (
example.com). - Repo —
owner/repo,https://github.com/owner/repo(.git), or[email protected]:owner/repo.git.
If either is missing, ask once via AskUserQuestion (free-text via "Other"). Never guess a repo.
Preflight (one command, before anything else):
for c in studio team51 git curl tar jq; do command -v "$c" >/dev/null 2>&1 || echo "MISSING: $c"; done
Stop and tell the user if anything is missing. team51 needs a loaded identity — if
1Password is locked it will prompt in the terminal; that is expected, not an error.
The database pull additionally needs a team51 build with the
*:download-site-database commands (on trunk since July 2026); team51 list
shows them if the CLI is current.
Step 1 — identify the site and pull its plugins
Always assume Pressable first. pull-site-plugins.sh does that, falls back to
WordPress.com only when Pressable reports the site as unknown, and reports which
host won along with the site's ID and URL.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/pull-site-plugins.sh" \
--site "<site-id-or-domain>"
This is the slowest step and the one most likely to fail (SSH/SFTP/auth), so it runs
before anything touches disk. Read RESULT_HOST, RESULT_SITE_ID, RESULT_SITE_URL
and RESULT_ARCHIVE from its output. RESULT_SITE_URL is the source site's own URL, and it
is what both the .local domain and the media fallback are derived from — this is the site
being mirrored, which is often a dev or staging box rather than the public production domain.
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.
- 4d ago First seen · 280 lines · 183 tokens per session scan A 35d47385d9a1
site-from-host is a skill published in the GitHub repository a8cteam51/claude-code-plugins (3 stars, last pushed 7d ago), licensed MIT. It adds 183 tokens to every session and 3,292 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.