Saiku is an open-source semantic layer that represents data as analytical cubes for browser exploration, SQL queries, dashboards, and AI-agent access. It is for analysts and applications that need to query structured business data through Mondrian, Apache Calcite, REST, or MCP. The catalogue instruction helps agents work with Saiku.
Borrowing it
Nothing to install: this file belongs to spiculedata/saiku. 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/spiculedata/saiku/development/.agents/skills/cut-release/SKILL.mdgit clone --depth 1 https://github.com/spiculedata/saikuWrote 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/spiculedata/saiku/cut-release)<a href="https://agentmods.dev/skills/spiculedata/saiku/cut-release"><img src="https://agentmods.dev/badge/skills/spiculedata/saiku/cut-release/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/spiculedata/saiku/cut-release"><img src="https://agentmods.dev/badge/skills/spiculedata/saiku/cut-release.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.00049 | $0.00558 |
| Opus 5.5 | $0.00020 | $0.00223 |
| Sonnet 5.5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
cut-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 1mo 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
Cut a release
Publishing is entirely CI-driven. Pushing a v* tag runs release.yml, which publishes the fat-JAR and dist zip (GitHub release assets), module jars (GitHub Packages), the Docker image (ghcr.io/spiculedata/saiku:<version>) and the npm embed package. Never mvn deploy locally.
- Bump the version on a branch off
development. Every reactor pom carries the literal release version (non-SNAPSHOT).mvn versions:set -DnewVersion=X.Y.Z -DgenerateBackupPoms=falseversions:setmissessaiku-bom/pom.xml, so fix that by hand. Check withgit grep -n '<version>OLD' -- '*pom.xml'. - Update
CHANGELOG.mdwith a section for the release, and fold in anydocs/release-notes-*-draft.md. Merge this todevelopmentvia PR. - Cut
release/X.Y.Zoffdevelopmentand push it.release-prep.ymlruns themvn verifygate. - Open a PR from
release/X.Y.Ztomainand merge it once green.gh pr mergecan silently no-op while a required check is pending. Before tagging, confirmmainactually advanced:git fetch && git log -1 origin/mainshould show the release merge and the new version. - Tag the merged
mainHEAD and push the tag.
If you tagged the wrong commit:git tag vX.Y.Z origin/main && git push origin vX.Y.Zgh run cancelthe release run,git push origin :refs/tags/vX.Y.Z,git tag -d vX.Y.Z, then re-tag correctly. - Replace the auto-generated release notes (a raw commit list) with the changelog section:
gh release edit vX.Y.Z --notes-file <file>. - Back-merge
mainintodevelopmentvia achore/back-merge-X.Y.ZPR. - Post-release: bump
LATEST_VERSIONintelemetry/wrangler.toml(PR todevelopment), and redeploy the demo box.
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.
- 1mo ago First seen · 27 lines · 49 tokens per session scan A 1adece660e7c
cut-release is a skill published in the GitHub repository spiculedata/saiku (1,334 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 558 once invoked, about $0.0002 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-29.
Other skills, from other repositories
lightdash-release-review
Review shipped Lightdash features and updates over a date range, on demand or on a schedule.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.