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/ractive/hyalo/releasenpx skills add ractive/hyalo --skill releasegit clone --depth 1 https://github.com/ractive/hyaloWhat 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.00102 | $0.01432 |
| Opus 5 | $0.00051 | $0.00716 |
| Sonnet 5 | $0.00020 | $0.00286 |
| Haiku 4.5 | $0.00010 | $0.00143 |
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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release hyalo
Cuts a release vX.Y.Z from main. The GitHub Release publish event is
what triggers the build/package pipeline (.github/workflows/release.yml,
shared via ractive/release-workflows) — so the release is created last,
after everything on main is final.
Hard rules
- NEVER create git tags manually.
gh release createmakes the tag. - CI enforces tag == workspace
Cargo.tomlversion; mismatch fails the pipeline after the tag exists — check the version BEFORE releasing. - Everything lands on
mainbefore the release is created. The mechanical release commits (version bump, changelog rotation) go directly on main — a release is a synchronous maintainer act; don't spin up a PR for them. - Every
hyaloinvocation below meanstarget/release/hyalo(build it first if stale). The barehyaloon PATH is the previously installed release — it predates the version being cut and will reject new config keys/flags (v0.18.0 example: it choked on[changelog]in.hyalo.tomland didn't knowlint --profile).
1. Preconditions
Decide the version from the [Unreleased] contents (pre-1.0 convention
here: minor bump for features/breaking, patch for fix-only), then run the
read-only preflight — it checks branch/clean/sync, the 3-spot version
match, that the tag doesn't exist, the changelog state (pre- vs
post-rotation), changelog-profile lint, and gh auth:
.claude/skills/release/scripts/release-preflight.sh check X.Y.Z
Fix every FAIL before proceeding. Additionally verify the latest merges are
green (gh run list --branch main --limit 5 / gh pr checks <last-PR>) —
the script cannot judge CI health.
2. Verify or bump the workspace version
Check the root Cargo.toml. The version appears in three places that
must all match the target:
[workspace.package] version = "X.Y.Z"hyalo-core = { path = ..., version = "X.Y.Z" }hyalo-mdlint = { path = ..., version = "X.Y.Z" }
Often the bump already happened during the dev cycle (e.g. 0.18.0 was bumped
in the changelog-conversion PR long before release day) — then just verify.
If a bump is needed: edit the three fields, run cargo build --release
(refreshes Cargo.lock — commit it too), run the full gates
(cargo fmt → cargo clippy --workspace --all-targets -- -D warnings →
cargo test --workspace -q), commit on main:
chore(release): bump version to X.Y.Z.
What ships with it
1 file 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.
- 3d ago First seen · 121 lines · 102 tokens per session scan A 2481fc6a9155
release is a skill published in the GitHub repository ractive/hyalo (24 stars, last pushed 3d ago), licensed MIT. It adds 102 tokens to every session and 1,432 once invoked, about $0.0005 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
writing-release-notes
Use when preparing, refreshing, backfilling, or redrafting a release-notes page under docs/releases/ before opening a normal review pull request.
setup
Scaffold a complete knowledge system. Detects platform, conducts conversation, derives configuration, generates everything. Validates against 15 kernel primitives. Triggers on "/setup", "/setup --advanced", "set up my knowledge system", "create my vault".
reduce
Extract structured knowledge from source material. Comprehensive extraction is the default — every insight that serves the domain gets extracted. For domain-relevant sources, skip rate must be below 10%. Zero extraction from a domain-relevant source is a BUG. Triggers on "/reduce", "/reduce [file]", "extract…
rethink
Challenge system assumptions against accumulated evidence. Triages observations and tensions, detects patterns, generates proposals. The scientific method applied to knowledge systems. Triggers on "/rethink", "review observations", "challenge assumptions", "what have I learned".
verify
Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".
architect
Research-backed evolution advice for your knowledge system. Analyzes health reports, friction patterns, and derivation history to propose specific changes with research justification. Never auto-implements — proposals require your approval.