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/sema-lisp/sema/releasegit clone --depth 1 https://github.com/sema-lisp/semaWhat 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.00000 | $0.01283 |
| Opus 5 | $0.00000 | $0.00642 |
| Sonnet 5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
release scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(e.g. `curl failed` / `HTTP2 framing layer` / `download of config.json failed`) How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a Release
Run the Sema release procedure end-to-end. $ARGUMENTS may contain the target
version (e.g. 1.21.2) or a bump kind (patch/minor/major); if absent,
infer the bump from the unreleased changes and confirm before tagging.
This mirrors Release Procedure in CLAUDE.md. Do the steps in order and stop
on the first failure — never tag or push a red build.
Step 1 — Pre-flight (run the FULL CI-equivalent suite; must be green)
Plain cargo test is NOT enough — CI also runs the example + bytecode smoke
tests, and a gap there once shipped a regression past four releases. Run what CI
runs:
cargo test --workspace # unit + integration tests
jake examples # smoke-test every .sema example (catches eval regressions)
jake smoke-bytecode # bytecode round-trip smoke test
jake lint # fmt-check + clippy -D warnings
jake docs-check # builtin doc index fresh
git status --short # the release commit should only bump version + Cargo.lock
Fix anything red before proceeding. The crates.io/npm publish workflows now gate
on a verify job (.github/workflows/verify.yml) running these same checks, so a
red suite blocks publishing — but catch it locally first to avoid a failed tag.
Step 2 — Choose the version
Read the top of CHANGELOG.md and the current version in Cargo.toml. Decide
the new X.Y.Z:
- patch — bug fixes only
- minor — new user-facing features / additive APIs
- major — breaking changes
If $ARGUMENTS didn't pin a version, state your choice and the reasoning.
Step 3 — Bump the version (13 lines: workspace + 12 inter-crate pins)
The #1 release footgun: there are 12 =OLD inter-crate pins plus the
workspace version. Bump all 13 in one shot, then verify the counts:
OLD=<current>; NEW=<target>
sed -i '' -e "s/^version = \"$OLD\"/version = \"$NEW\"/" -e "s/version = \"=$OLD\"/version = \"=$NEW\"/g" Cargo.toml
grep -c "$NEW" Cargo.toml # expect 13
grep -c "$OLD" Cargo.toml # expect 0
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 · 131 lines · 0 tokens per session scan A 7765879d3713
release is a command published in the GitHub repository sema-lisp/sema (39 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,283 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
release-harn
Run the tag-first Harn release workflow.
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
release
You are a release agent for the Rivet project. Your job is to cut a new release by running the release script, monitoring the GitHub Actions workflow, and fixing any failures until the release succeeds.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Command "release" from Besty0728/Unity-Skills, covering release workflow — 候选矩阵 → main/tag → 正式 release, 输入, 阶段 1：只读预检查, 阶段 2：生成并审阅 release note and v{version} — {一句话总结，提炼 2-4 个核心特性}.