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 commands/generous-corp/pulp/ci-hostgit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/commands/generous-corp/pulp/ci-host)<a href="https://agentmods.dev/commands/generous-corp/pulp/ci-host"><img src="https://agentmods.dev/badge/commands/generous-corp/pulp/ci-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.00023 | $0.00412 |
| Opus 5 | $0.00012 | $0.00206 |
| Sonnet 5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
ci-host 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
pulp ci-host is the optional, discoverable wrapper around
tools/ci/setup-ci-host.sh for turning a Mac into a Tart-VM CI host. It is an
advanced/contributor path — never required, and Shipyard stays
encouraged-not-mandated. The real work lives in the script; the command just
makes it discoverable and passes flags through.
Setup a host
pulp ci-host setup --class <m5|studio|macbook|...> # minimum
pulp ci-host setup --class m5 --copy-from 'macstudio:/Volumes/Workshop/VMs/vms/pulp-build-runner:latest'
pulp ci-host setup --class m5 --validate # also run a one-shot VM build to prove it
Common flags (all forwarded to setup-ci-host.sh):
--class <name>— required host class for the runner label (m5,studio,macbook, …)--copy-from <ssh:path | path>— rsync a golden in from another host/drive (sparse-safe)--validate— after setup, run one ephemeral VM build on the host-only label--no-agent— do everything except install/load the launchd agent
Run pulp ci-host setup --help for the full flag list.
Notes
- Runs from inside a Pulp checkout (it resolves
tools/ci/setup-ci-host.sh). - For the from-scratch host recipe and gotchas, see
docs/guides/mac-ci-host-setup.mdand thetart-ciskill. - The bare-metal runner lane is a different tool; this command is the Tart-VM (ephemeral per-job) host path.
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 First seen · 36 lines · 23 tokens per session scan A 5522ede47806
ci-host is a command published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 412 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.