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 Mickdownunder/SafeInstall --skill safeinstall-setupgit clone --depth 1 https://github.com/Mickdownunder/SafeInstallWrote 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/mickdownunder/safeinstall/safeinstall-setup)<a href="https://agentmods.dev/skills/mickdownunder/safeinstall/safeinstall-setup"><img src="https://agentmods.dev/badge/skills/mickdownunder/safeinstall/safeinstall-setup/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/mickdownunder/safeinstall/safeinstall-setup"><img src="https://agentmods.dev/badge/skills/mickdownunder/safeinstall/safeinstall-setup.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.00049 | $0.00499 |
| Opus 5.5 | $0.00020 | $0.00200 |
| Sonnet 5.5 | $0.00010 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
safeinstall-setup 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 2d 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
Set up SafeInstall
Last verified: 2026-10-01
Resolve this skill's installed directory from the host-provided skill location.
The plugin root is two directories above this skill directory. Use that absolute
root, never a guessed cache path or a global safeinstall binary. Quote all paths.
Do not assume PLUGIN_ROOT is exported in an ordinary shell tool; it is a hook variable.
- Resolve the user's intended project to an absolute directory. If there are
multiple plausible projects, ask which one. Check Node.js satisfies
^22.22.2 || ^24.15.0 || >=26.0.0, required by bundled signature verification. If unsupported, ask the user to select a supported runtime; do not install one or weaken provenance policy automatically. - Call the plugin's
protection_statuswith thatprojectPath. Report policy presence, trust drift, and the distinction between policy and hook activation. - Explain the writes before asking permission: starter
safeinstall.config.jsonand.safeinstall/baseline/ledger. Existing policy is preserved; existing trust drift stops setup. Do not run setup without the user's authorization. - In the project directory, run:
node "<absolute-plugin-root>/scripts/run.cjs" cli init --no-guard --mode strict --jsonThe host owns the plugin hook. Do not add duplicate project hooks. - Call
protection_statusagain. If drift is reported, show it and stop. Never approve drift, unlock trust, remove a lock, use--force, lower policy, or grant hook trust on the user's behalf. - Tell the user to review and explicitly trust the bundled hook in the host's hook trust UI and start a new chat if needed. Installation alone does not enable enforcement. Do not report “protected” without observing activation.
No API key or package download is required by this plugin. Registry package checks still contact the project's configured registry. Local hooks protect supported shell-tool calls, not arbitrary code execution or all system installs.
What ships with it
1 file beside SKILL.md 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.
- 2d ago First seen · 38 lines · 49 tokens per session scan A 1abfb755871f
safeinstall-setup is a skill published in the GitHub repository Mickdownunder/SafeInstall (3 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 499 once invoked, about $0.0002 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-10-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…