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 alswl/skm --skill skillgit clone --depth 1 https://github.com/alswl/skmWrote 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/alswl/skm/skill)<a href="https://agentmods.dev/skills/alswl/skm/skill"><img src="https://agentmods.dev/badge/skills/alswl/skm/skill/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/alswl/skm/skill"><img src="https://agentmods.dev/badge/skills/alswl/skm/skill.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.00109 | $0.01325 |
| Opus 5.5 | $0.00044 | $0.00530 |
| Sonnet 5 | $0.00022 | $0.00265 |
| Haiku 4.5 | $0.00011 | $0.00133 |
Grade A, and why
skm 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skm
skm keeps skills and commands in one local Git repo and installs them into every
tool. Two axes: providers say where an asset came from; targets say where it
gets installed. skm --help and docs/cli/ have the full surface — this file is the
working model plus the commands worth reaching for.
Before anything else
- Every command takes
--json. Always pass it when you're going to parse the output; the human tables are not a stable contract. - Exit codes:
0ok,1problem with the object you asked about,2argument / tool / provider error. Don't infer success from stdout. - The repo root is discovered upward from cwd (a
skills/orcommands/dir marks it); override with--root, orSKM_ROOT. If a command says "no repository found", you are outside the repo — pass--root, don'tskm inita new one. --dry-runreports intended actions and writes nothing. Use it first for anything that touches target directories.- Destructive commands (
delete,delete-external) require--forceby design. Ask the user before reaching for them.
The loop that covers most work
skm list --json # the catalog: every entry, with install columns
skm status <name> --json # one entry across targets: installed/dangling/drifted
skm install <name> [--target t] # default: every kind-matching target
skm uninstall <name> [--target t] # removes managed installs only, never user files
skm verify --json # whole-repo consistency
Bringing assets in:
skm import ./my-skill --kind skill # local path
skm import owner/repo/path/to/skill --json # GitHub shorthand, subdir, or a blob URL
skm import - < sources.txt # newline-separated list on stdin
skm discover --json && skm adopt ~/.codex/skills/review # take over an unmanaged install
skm update <name> / skm batch-update # refresh from the recorded origin
Entries are plain directories with SKILL.md; editing files in the repo is normal
and expected. Never edit an installed copy in a target — it is a symlink or a
generated adapter, and drift is what skm status will report.
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 First seen · 118 lines · 109 tokens per session scan A 44274ce3514d
skm is a skill published in the GitHub repository alswl/skm (6 stars, last pushed 4d ago), licensed MIT. It adds 109 tokens to every session and 1,325 once invoked, about $0.0004 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-09-25.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run repeated, measured Git experiments toward a numeric target; keep improvements and revert failures. Use for autonomous optimization or managing an autoresearch run, not one-shot edits.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…