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 skills/stack-cairn/liveagent/skills-installernpx skills add Stack-Cairn/LiveAgent --skill skills-installergit clone --depth 1 https://github.com/Stack-Cairn/LiveAgentWrote 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/stack-cairn/liveagent/skills-installer)<a href="https://agentmods.dev/skills/stack-cairn/liveagent/skills-installer"><img src="https://agentmods.dev/badge/skills/stack-cairn/liveagent/skills-installer.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.00062 | $0.00743 |
| Opus 5 | $0.00031 | $0.00371 |
| Sonnet 5 | $0.00012 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
skills-installer 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 4d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Installer
Install LiveAgent skills into the fixed runtime root while preserving existing user data.
Workflow
- Determine the source type: ClawHub slug/search result, local skill directory,
.zipor.skillarchive, HTTP(S) download, or GitHub URL. - Determine the target destination. Runtime installs always go through
SkillsManagerinto LiveAgent's fixed user Skills root. - For local workspace sources, pass workspace-relative paths such as
./my-skillor./dist/my-skill.skill; LiveAgent resolves them against the current chat workspace before installing into the fixed skills root. - Read
references/install-sources.mdandreferences/safety-and-conflicts.mdthrough file tools before replacing anything. Usepath="skill://skills-installer/references/install-sources.md"andpath="skill://skills-installer/references/safety-and-conflicts.md", or use the exactpathRefreturned by a prior tool. - Use
SkillsManagerwithaction=listto inspect the skills enabled in the current conversation when conflict or inventory context matters. - Use
SkillsManagerwithaction=clawhub_searchto find ClawHub skills when the user asks to search the public store, then useaction=clawhub_installwith the returnedslugto install from ClawHub. - Use
SkillsManagerwithaction=installto import a direct local, archive, HTTP(S), or GitHub source. Preferconflict=backupunless the user explicitly accepts replacement. - After installation, the new skill is enabled for the current conversation automatically; ask LiveAgent to rescan skills or reopen the Skills menu only if the new skill does not appear immediately.
Commands
SkillsManager(action=list)
SkillsManager(action=clawhub_search, query=memory, limit=10)
SkillsManager(action=clawhub_search, sort=downloads, limit=10)
SkillsManager(action=clawhub_install, slug=example-skill, conflict=backup)
SkillsManager(action=install, source=./my-skill)
SkillsManager(action=install, source=./dist/my-skill.skill)
SkillsManager(action=install, source=https://github.com/owner/repo/tree/main/skills/my-skill)
SkillsManager(action=validate, name=my-skill)
SkillsManager(action=package, name=my-skill)
What ships with it
2 files 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.
- 4d ago First seen · 42 lines · 62 tokens per session scan A fafcbe4462ae
skills-installer is a skill published in the GitHub repository Stack-Cairn/LiveAgent (1,913 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 743 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
himalayas-employer
AI hiring assistant for Himalayas. Post remote jobs, manage company profiles, source talent, message candidates, and benchmark salaries using the Himalayas MCP server.
che-word-mcp
A Swift-native MCP server for Microsoft Word (.docx) document manipulation. Provides 83 tools for reading, writing, and modifying Word documents without requiring Microsoft Word installation.
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
live-audit
Repo-specific playbook, for any agent/model working on this repo (not tied to a particular harness — see AGENTS.md's own framing). Use it when asked to test/audit/smoke-test the published tmdb-mcp package, hunt for bugs or edge cases, or repeat "the same kind of testing as before.".
prompt-check
Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.
prompt-check
Live-test every MCP Prompt in src/prompts.ts through the real MCP protocol (not a static read) across every argument combination, including every enum value. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.