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 stark-ai-de/agent-skills --skill skill-installation-supportgit clone --depth 1 https://github.com/stark-ai-de/agent-skillsWrote 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/stark-ai-de/agent-skills/skill-installation-support)<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/skill-installation-support"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/skill-installation-support/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/stark-ai-de/agent-skills/skill-installation-support"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/skill-installation-support.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.00066 | $0.00741 |
| Opus 5.5 | $0.00026 | $0.00296 |
| Sonnet 5.5 | $0.00013 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
skill-installation-support 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Installation Support
Goal
Help users install, list, update, remove, and troubleshoot Agent Skills with clear commands and safe distinctions between local, global, and agent-specific installation.
When to use
- The user asks how to install a skills repo or one skill.
npx skills@latest addfails or does not discover expected skills.- The user asks about Codex, Claude Code, Cursor, or all-agent installation targets.
When not to use
- The user wants to create or review a skill; use
skill-authoring-review. - The user wants to maintain this repository's catalog or release state; use
skill-repo-curator. - The source skill has unclear provenance or license and should not be installed yet.
Inputs
- Repository path or GitHub owner/repo.
- Desired skill name, target agent, and global or project install preference.
- Error output from
npx skills@latest. - Local
skills/tree andSKILL.mdfrontmatter when troubleshooting discovery.
Inputs to inspect
- Inspect the source path or repository, requested skill name, target agent, global/project scope, and CLI error output.
- Check
SKILL.mdnames and descriptions when discovery fails.
Process
- Identify source: local folder, GitHub repo, full Git URL, or specific skill.
- List skills before installing when the source is unfamiliar.
- Choose global or project install based on the user's scope.
- Choose target agent flag based on the user's runtime.
- Troubleshoot discovery by checking folder structure,
SKILL.md, name matching, and CLI output. - Avoid global installation or overwrites without user approval.
Workflow
Follow the process above, then return a copy-pasteable command plus a verification command before suggesting any global install.
Decision points
- Use
--listbefore installation for unfamiliar repos. - Use
--skill <name>when installing one skill from a multi-skill repo. - Use
--allonly when the user wants all supported agents. - Prefer local folder install for testing unpublished repos.
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.
- 1mo ago First seen · 97 lines · 66 tokens per session scan A c923c0d659dd
skill-installation-support is a skill published in the GitHub repository stark-ai-de/agent-skills (8 stars, last pushed 3d ago), licensed Apache-2.0. It adds 66 tokens to every session and 741 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
claude-delegate
Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the claude CLI — for example, "have another Claude implement…
warp-delegate
Delegate a coding task to the Warp Agent CLI (oz) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Warp - phrasings like "have Warp implement X", "delegate this to the Warp CLI", "run it through Warp", "use oz to…
zcode-delegate
Delegate a coding task to the Z.AI ZCode CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to ZCode — phrasings like "have ZCode do X", "delegate this to ZCode", "run it through ZCode", or "use ZCode to implement/fix/refactor" — or…
cline-delegate
Delegate a coding task to the Cline coding agent CLI (cline) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Cline - phrasings like "have Cline implement X", "delegate this to cline", "run it through Cline", or "use cline to…
kimi-delegate
Delegate a coding task to the Kimi Code CLI (kimi) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Kimi - phrasings like "have Kimi implement X", "delegate this to Kimi", "run it through Kimi Code", or "use Kimi to…
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.