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 madarco/agentbox --skill agentbox-infogit clone --depth 1 https://github.com/madarco/agentboxWrote 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/madarco/agentbox/agentbox-info)<a href="https://agentmods.dev/skills/madarco/agentbox/agentbox-info"><img src="https://agentmods.dev/badge/skills/madarco/agentbox/agentbox-info/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/madarco/agentbox/agentbox-info"><img src="https://agentmods.dev/badge/skills/madarco/agentbox/agentbox-info.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 71 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 151 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 172 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 212 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 284 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00079 | $0.06788 |
| Opus 5.5 | $0.00032 | $0.02715 |
| Sonnet 5.5 | $0.00016 | $0.01358 |
| Haiku 4.5 | $0.00008 | $0.00679 |
Grade A, and why
agentbox-info 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 28d 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.
**The id is a safety token — inspect, then approve that exact id.** `approve <id>` answers the specific prompt you listed; if a *different* prompt has since taken its place, the recomputed id won't match and the approve How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentBox (host-side)
You are operating on the user's host machine (laptop / dev workstation), not inside a box. Use the agentbox CLI to provision isolated sandboxes for coding agents and to attach to them.
If you find yourself inside a box (/workspace exists and AGENTBOX_RELAY_URL is set in the env), this is the wrong skill — use the in-box /agentbox-setup skill instead.
What AgentBox is, in one paragraph
AgentBox spins up one isolated sandbox per agent run — a local Docker container (default), a Hetzner VPS (--provider hetzner), a Vercel Sandbox (--provider vercel), an E2B microVM (--provider e2b), or a Daytona cloud sandbox (--provider daytona, partial support). Each box has its own /workspace, but the host's .git/ is shared, so commits made inside the box land on the host immediately. The agent inside the box has no host credentials — git push, opening URLs in the host browser, capturing checkpoints, and all other host-side operations flow through a small host process called the relay that runs alongside the CLI.
The two starting commands
agentbox create
Provision a box and stop. The box exists and is ready, but nothing is launched inside it.
agentbox create # docker, auto-named after the workspace
agentbox create -n review # docker, friendly name
agentbox create --provider hetzner # cloud VPS (requires `agentbox prepare --provider hetzner` once)
agentbox create --attach # drop into a shell inside the box after create
Useful flags: -n <name> (friendly box name), --provider docker|daytona|hetzner|vercel|e2b, --attach, -w <path> (workspace to mount; defaults to cwd), --snapshot <ref> (start from a checkpoint).
Non-docker providers require a one-time agentbox prepare --provider <name> to bake the base image / snapshot.
agentbox claude
Provision (same as create) and launch Claude Code inside the box, in a detachable tmux session. This is the main entry point most users want.
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.
- 28d ago Changed · +37 lines 508f88f1c4d3
- 1mo ago Changed · +21 lines f2d5e5980379
- 1mo ago Changed cb3046a4668a
- 1mo ago Changed d9d609d98a9a
- 1mo ago First seen · 285 lines · 79 tokens per session scan A b511fb4022f9
agentbox-info is a skill published in the GitHub repository madarco/agentbox (538 stars, last pushed 13d ago), licensed MIT. It adds 79 tokens to every session and 6,788 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
04-security
A security and operations guide for deploying Dify, an open-source platform for building AI applications, in production.
harbor
CLI toolkit for managing containerized LLM services. Use when the user wants to start, stop, configure, or manage AI/LLM services like Ollama, Open WebUI, llama.cpp, vLLM, LiteLLM, ComfyUI, and 250+ others. Triggers on requests to "run a model", "start ollama", "set up an LLM", "configure harbor", "manage services"…
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
docker
Use when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is deployment), NOT k8s autoscaling (that is scaling), NOT app-level injection or secrets-in-code…
ilo
Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the ilo CLI instead of on the host. Use this whenever a project relies on ilo, devcontainers, or container-based build environments — it has a .ilo.rc / .ilo/ilo.rc, dev/ argument files, a Containerfile/Dockerfile, a…
write-dockerfile
Creates or updates an optimized, production-ready Dockerfile and .dockerignore. Focuses on image build strategy, runtime hardening, caching, and minimal production images. Invoked when the user asks to write a Dockerfile, improve container image quality, or harden image builds.