Borrowing it
Nothing to install: this file belongs to Kemetra/Seshat-BI. 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/Kemetra/Seshat-BI/main/.claude/skills/capabilities/SKILL.mdgit clone --depth 1 https://github.com/Kemetra/Seshat-BIWrote 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/kemetra/seshat-bi/capabilities)<a href="https://agentmods.dev/skills/kemetra/seshat-bi/capabilities"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/capabilities.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.1 | $0.00048 | $0.00583 |
| Opus 5 | $0.00024 | $0.00292 |
| Sonnet 5 | $0.00010 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
capabilities 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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capabilities
The read-only capability inventory: one truthful, categorical read of everything Seshat BI can do, derived from committed, reviewable metadata (never from a file's mere existence).
What it does
Reads the committed capability manifest (docs/capabilities/capabilities.yaml)
and reconciles it against the feeders that already own each fact -- the
_DISPATCH command table, .claude/skills/*/SKILL.md frontmatter,
.seshat/kit-source.yaml verbs, docs/roadmap/roadmap.md F-numbered ship
status, and docs/quality/status-claims.yaml -- then renders:
- a grouped human-readable read (the default), or
- a stable, deterministic JSON machine form (
--format json).
How to invoke it
Run the module directly from the repo root:
python -m seshat.capability_inventory
python -m seshat.capability_inventory --format json
There is no retail capabilities / seshat capabilities CLI verb -- this is a
deliberate, ratified choice (docs/roadmap/decisions/cli-verbs-vs-skill-driven.md,
Option B). Do not add one; do not touch src/seshat/cli/parser.py or
_DISPATCH to "wire this up". Simply run the module command above and relay
its output.
What it is NOT
- Not a gate. It adds no
seshat checkrule; its presence/absence never blocks anything. - Not a readiness surface. It reads no
readiness-status.yaml, moves no stage, grants no approval. For per-table readiness useseshat status; for the next allowed action useseshat next; for repo drift useseshat doctor; for the governance gate useseshat check. - Not a scoring surface. No maturity/confidence/completeness/health value is ever emitted, and nothing is ranked by a computed number.
- Not a writer. It writes nothing, connects to no database, runs no Power BI.
See also
docs/capabilities/README.md-- the fail-closed truthfulness contract and how this differs fromstatus/next/doctor/check.docs/capabilities/capabilities.yaml-- the manifest this skill renders.
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.
- 7d ago First seen · 57 lines · 48 tokens per session scan A 1b96095c6c59
capabilities is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 48 tokens to every session and 583 once invoked, about $0.0002 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 skills, from other repositories
ktx-analytics
Use when answering a question that needs data from a ktx-connected database - investigating, analyzing, "how many", "show me", "what's the breakdown of", finding records by value, exploring tables, comparing periods, explaining metrics, or any data-analysis request. Triggers even when the user does not say…
metabase_ingest
Convert Metabase questions, models, and metrics into ktx Semantic Layer source definitions. Covers result-metadata to KSL column type mapping, FK/PK detection, near-duplicate deduplication, pre-aggregation decomposition, join-graph connectivity, and how to react to priorProvenance from earlier ingest syncs. Load when…
sl_capture
How to capture new reusable patterns into ktx's semantic layer - when a measure, segment, or join belongs in the catalog and how to write it generically so it stays small and useful over time. Loaded by the post-turn memory-agent only. The research agent does not write to the SL.
looker_ingest
Extract durable ktx knowledge and semantic-layer contribution proposals from staged Looker runtime dashboard, Look, and explore JSON. Load for WorkUnits whose raw files are under explores/, dashboards/, or looks/.
metricflow_ingest
Map a MetricFlow semanticmodel or metric into ktx semantic layer sources. Covers the MetricFlow to ktx primitive table, extends: inheritance flattening, metric-type handling (simple / derived / ratio / cumulative / conversion), model: ref('x') resolution, and four worked examples. Load when the turn contains…
lookml_ingest
Map a LookML view/model/explore into ktx semantic layer sources. Covers the LookML to ktx primitive table, provenance tagging, and three worked examples (overlay, standalone from derivedtable, standalone with sqlalwayswhere). Load when the turn contains .lkml content.