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 skills add ScriptedAlchemy/agent-bundle --skill host-testgit clone --depth 1 https://github.com/ScriptedAlchemy/agent-bundleWrote 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/scriptedalchemy/agent-bundle/host-test)<a href="https://agentmods.dev/skills/scriptedalchemy/agent-bundle/host-test"><img src="https://agentmods.dev/badge/skills/scriptedalchemy/agent-bundle/host-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/scriptedalchemy/agent-bundle/host-test"><img src="https://agentmods.dev/badge/skills/scriptedalchemy/agent-bundle/host-test.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00331 |
| Opus 5.5 | $0.00012 | $0.00132 |
| Sonnet 5.5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
host-test 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 1mo 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
Host test probe
This plugin records every hook event the host dispatches to it, plus every call to its own MCP servers, into one NDJSON log and a durable state summary. Nothing it records is sent anywhere; the log stays on this machine.
Inspect or probe
For a log or identity question, call the host-test MCP server's dump tool
and report the relevant observed ids and log path. Existing records may answer
the question without a live probe. The dump call itself is recorded;
distinguish absent evidence from an unsupported host capability.
For a requested live probe, generate only the evidence needed:
- Run a harmless shell command such as
pwdfor tool-hook evidence. - Create a small scratch file for file-edit-hook evidence.
- If
host-test-rawexposesprobe, call it with your role (rootorsubagent) as the note. - For parent/subagent lineage, ask a subagent to run the shell and available probe calls, then dump the resulting records. A log-only request does not require spawning an agent.
Dump the resulting records and report the relevant ids verbatim, without editing the log. Do not include unrelated payloads in the response.
Never delete or rewrite the log by hand; the reset tool is the only way to
clear it, and only when the user asks for a fresh probe.
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.
- 1mo ago Changed · +6 tokens per session 1c2157429ac8
- 1mo ago Changed · +1 lines · -23 tokens per session 1c327f0998e2
- 1mo ago First seen · 33 lines · 47 tokens per session scan A 7b931959fc87
host-test is a skill published in the GitHub repository ScriptedAlchemy/agent-bundle (11 stars, last pushed 8d ago), licensed Apache-2.0. It adds 30 tokens to every session and 331 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.