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.
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 instructions/spiculedata/saiku/claude-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/instructions/spiculedata/saiku/claude-md)<a href="https://agentmods.dev/instructions/spiculedata/saiku/claude-md"><img src="https://agentmods.dev/badge/instructions/spiculedata/saiku/claude-md.svg" alt="Measured on agentmods" 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 | $0.06024 | $0.06024 |
| Opus 5 | $0.03012 | $0.03012 |
| Sonnet 5 | $0.01205 | $0.01205 |
| Haiku 4.5 | $0.00602 | $0.00602 |
Grade A, and why
saiku CLAUDE.md 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 5d 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.
The PAT must be a **classic** token with the `read:packages` scope — [GitHub only supports classic PATs for the Maven registry](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the 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.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build, test, run
JDK 22 + Maven 3.9+ are required to build the full reactor. JDK 22 is needed only because saiku-proptest (Hegel property tests) uses the Foreign Function & Memory API + a bundled native engine, which is Java-22 bytecode. Main artifacts still compile at release 21, so the shipped runtime (Docker image, launcher fat-JAR) is unchanged and still runs on JRE 21+. To build without JDK 22, skip the module: mvn -pl '!saiku-proptest' verify. The reactor is saiku-bom → saiku-core → saiku-webapp → saiku-launcher → saiku-proptest. saiku-ui is a separate SvelteKit app and is not a reactor module — but mvn verify still builds it, via saiku-webapp's frontend plugin (see Testing baseline), so a cold build downloads a Node toolchain.
On Windows, set git config core.autocrlf false and re-clone before building. Git for Windows defaults core.autocrlf=true, and the repo has no .gitattributes to override it, so checkout rewrites every LF blob to CRLF and spotless:check then rejects every Java file — before anything compiles. CI never catches this because CI is Linux-only.
mvn verify # compile + unit tests + spotless:check (CI's gate)
mvn spotless:apply # auto-format Java (Palantir Java Format, bound in root pom)
mvn -pl saiku-core/saiku-service -am test # one module's tests
mvn -pl saiku-core/saiku-service test -Dtest=RepositoryDatasourceManagerTest # single test class
mvn -pl saiku-webapp,saiku-launcher clean # WIPE stale UI bundles before rebuilding — CRITICAL for UI changes
mvn -pl saiku-launcher -am -Dmaven.test.skip=true package # build the runnable fat-JAR
mvn -P security verify # OWASP dependency-check (opt-in)
./scripts/install-hooks.sh # one-time: install pre-commit spotless hook
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.
- 5d ago First seen · 118 lines · 6,024 tokens per session scan A a60d12f87a06
saiku CLAUDE.md is an instructions file published in the GitHub repository spiculedata/saiku (1,320 stars, last pushed 4d ago), licensed Apache-2.0. It adds 6,024 tokens to every session, about $0.0301 per session on Opus 5. 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 instructions, from other repositories
evidence AGENTS.md
AGENTS.md instructions for evidence-dev/evidence, covering agents.md, this repo is a mirror, layout and scripts.
cloudflare-docs AGENTS.md
AGENTS.md instructions for cloudflare/cloudflare-docs, covering agents.md — cloudflare docs, repository overview, directory structure, content — writing and editing docs and file locations.
drizzle-cube CLAUDE.md
Claude Code instructions for cliftonc/drizzle-cube, covering claude.md, project structure, agent documentation context, database support and essential commands.
publisher AGENTS.md
AGENTS.md instructions for malloydata/publisher, covering working with malloy publisher, what you can do, 1. start the server first, 2. connect your agent and 3. the mcp tools.
blog AGENTS.md
Instructions for sabertaz/blog, covering agents.md, quick start, first time setup, development and common tasks.
horizun-pbi-mcp AGENTS.md
AGENTS.md instructions for HorizunGroup/horizun-pbi-mcp, covering repository rules for agents, 1. before touching anything, 2. the mcp contract is untouchable, 3. invariants no phase can break and 4. real data: never enters git.