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 commands/aliasunder/agent-skills/releasegit clone --depth 1 https://github.com/aliasunder/agent-skillsWhat 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.00017 | $0.00356 |
| Opus 5 | $0.00009 | $0.00178 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
release 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
Release
Bump the version in package.json, commit, tag, and push. The CI release workflow handles building artifacts and creating the GitHub release.
Steps
-
Get bump type: Use the
bumpargument if provided. Otherwise ask the user to choose: patch, minor, or major. -
Read current version from
package.jsonfieldversion. -
Calculate next version by incrementing the chosen segment:
- patch:
1.0.0→1.0.1 - minor:
1.0.0→1.1.0 - major:
1.0.0→2.0.0
- patch:
-
Update package.json: Set
versionto the next version. Usejqfor the edit to preserve formatting. -
Confirm with user: Show the version change and the file modified. Ask for confirmation before committing.
-
Commit + tag + push:
- Stage
package.json - Commit with message:
release: vX.Y.Z - Create tag:
vX.Y.Z - Push commit and tag to origin
- Do NOT add Co-Authored-By lines
- Stage
-
Report: Tell the user the release is in progress and link to the Actions tab:
https://github.com/aliasunder/agent-skills/actions
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 · 37 lines · 17 tokens per session scan A de9038d72cde
release is a command published in the GitHub repository aliasunder/agent-skills (4 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 356 once invoked, about $0.0001 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-31.
Other commands, from other repositories
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
tldr-help
Quick reference card for tldr modes, slash commands, and triggers.
tldr-review
One-line TLDR PR review comments (verdict first, no filler).
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
context
上下文管理，加载项目信息（会话级，另见 /cc-best:memory 管理持久记忆）.
infer
Command "infer" from xiaobei930/cc-best, covering /infer - 模型推理, 适用场景, 通用推理流程, 1. 环境检查 and gpu 检查.