Borrowing it
Nothing to install: this file belongs to lukacf/meerkat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lukacf/meerkat/main/.claude/skills/meerkat-cli-reference/SKILL.mdgit clone --depth 1 https://github.com/lukacf/meerkatWrote 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/lukacf/meerkat/meerkat-cli-reference)<a href="https://agentmods.dev/skills/lukacf/meerkat/meerkat-cli-reference"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/meerkat-cli-reference/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/lukacf/meerkat/meerkat-cli-reference"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/meerkat-cli-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Rogue Agent · line 136 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.
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.00037 | $0.11131 |
| Opus 5.5 | $0.00015 | $0.04452 |
| Sonnet 5.5 | $0.00007 | $0.02226 |
| Haiku 4.5 | $0.00004 | $0.01113 |
Grade A, and why
meerkat-cli-reference 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 3d 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 — 759 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meerkat CLI Reference
Use this skill as the exact authority for rkat shell commands. Command
spelling, singular/plural forms, flags, and enum values matter.
Hard Negative Facts
- There is no
rkat sessions,rkat realms, orrkat skills; use singularrkat session,rkat realm,rkat skill. - There is no
rkat resume,rkat continue, orrkat c; userkat run --resume .... - There is no
rkat rpc; use therkat-rpcbinary for JSON-RPC. - An unknown first word is not rejected as a command: it becomes the prompt,
so
rkat rpcrunsrkat run rpc(extra unquoted words then fail to parse). Only the legacy names above are refused. rkat-rpc --tcpis not a Meerkat signed peer/comms listener; userkat run --comms-listen-tcp ...for remote peers and external mob members.- There is no root
rkat livegroup. Use JSON-RPClive/*for ordinary sessions; mob members (local or placed) also have therkat mob livegroup, WebSocket only. - There is no
rkat imagecommand. - There is no
rkat schedulecommand; manage schedules through JSON-RPCschedule/*, REST/schedules, the SDK schedule helpers, or the agentmeerkat_schedule_*tools insiderkat run. - There is no
rkat mcp reloadCLI command. - There is no
rkat mcp logout; sign out with RPCauth/logoutand anmcptarget (Pythonauth_mcp_logout, TypeScriptauthMcpLogout). There is no CLI command to set MCP service secrets (secret_envvalues); a Rust host usesmeerkat::set_mcp_service_secret. - There is no
--tools all; valid values aresafe,workspace,full,none. - OS sandboxing is off unless the
[confinement]config section or the root--confinement <trusted-host|workspace>flag turns it on; without themrkatruns shell commands, command hooks and stdio MCP servers as trusted host processes.--tools none, the shell'srestrict_to_projectcheck and--isolatedare not OS sandboxes. Seereferences/security.mdof the meerkat-platform skill. rkat blob gethas no-oor--out; use--output <FILE>.rkat session showhas no--jsonflag.rkat modelsandrkat capabilitiestake no arguments (no--json/--format, norkat models catalog) and already print pretty JSON.rkat doctor(setup checks, no flags) andrkat storage doctor(storage diagnosis,--json/--root) are different commands.rkat storage prunedeletes only registered maintenance backup artifacts; realm deletion isrkat realm delete/rkat realm prune.--isolatedand--default-modelcannot be combined withrkat storage; both are usage errors (exit 2).rkat mob hostalso rejects--isolated.rkat runhas no hook flags; per-session hook overrides (hooks_override) exist only on RPC, REST, MCP and the SDKs.- There is no manual compaction command on any surface.
rkathas no JSON-lines event output;--output jsonprints only the final result.rkat session interruptcannot stop a turn running in another process.
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.
- 3d ago Changed · +20 lines 1b5ed8277b31
- 10d ago Changed · +11 lines a99421a7ec6d
- 13d ago Changed · +173 lines 02a283a0b479
- 19d ago Changed · +6 lines 18b83f0908ac
- 1mo ago Changed · +22 lines 0188eb5982cf
- 1mo ago Changed 4e0c820eab00
- 1mo ago First seen · 527 lines · 37 tokens per session scan A 5b67c6da592a
meerkat-cli-reference is a skill published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 11,131 once invoked, about $0.0001 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-30.
Other skills, from other repositories
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.