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/approval-console/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/approval-console)<a href="https://agentmods.dev/skills/kemetra/seshat-bi/approval-console"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/approval-console/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/kemetra/seshat-bi/approval-console"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/approval-console.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.00048 | $0.03718 |
| Opus 5 | $0.00024 | $0.01859 |
| Sonnet 5 | $0.00010 | $0.00744 |
| Haiku 4.5 | $0.00005 | $0.00372 |
Grade A, and why
approval-console 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 9d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
approval-console
- Roadmap feature: F027. On-disk spec:
specs/021-approval-console/. When the spec-dir number (021) and the roadmap F-number (F027) disagree, the roadmap F-number wins: this is F027.
The kit STOPS at judgment calls (Principle V) and the readiness spine RESERVES the slot
for the answer (readiness-status.yaml approvals[]; the unresolved-questions.md
Open-questions Resolution column). What it lacks is the LOOP between "a question was
raised" and "the named human's answer is recorded in the committed artifacts". This skill
is that loop, and only that loop. It does two things: (1) packages a raised judgment call
into a reviewable DECISION PACKAGE (a request), and (2) once a named human answers,
RECORDS that decision back into the committed artifacts. An approval that lives only in
chat is not an approval -- it cannot be reviewed, advance a gate, or be audited.
Authority declaration (F024 module contract -- filled)
- Authority category: Product Module
- Capability level:
artifact-writing(exactly one) - Product layer: 1-6 (all stages -- the functional axis; orthogonal to category)
- Roadmap feature: F027 On-disk spec:
specs/021-approval-console/ - Owner: the named human who decides each judgment call (the console transcribes; it is never the owner)
- Status: Authored (skill + two templates + one docs page; no runtime code)
What it does (one line)
Consumes a raised judgment call + a named human's answer, and WRITES the transcribed decision through to the committed
unresolved-questions.mdResolution + thereadiness-status.yamlapprovals[]slot -- it never authors the decision itself.
Project-scoped target: provisioning approvals (spec 154 / #671)
Most approvals this console transcribes are PER-TABLE, into
mappings/<table>/readiness-status.yaml approvals[]. One is PER-PROJECT:
authorizing the installation of external software.
- Target:
contracts/provisioning-approvals.yaml-- never a per-table readiness record. Provisioning authority is about the project's environment and tooling, not one table's readiness, and the gate refuses a provisioning approval found under amappings/<table>/path. - Row shape:
stage: provisioning,owner: "<Person Name> (governance)",at: <YYYY-MM-DD>,components: [<ids>], optionalnote, optionalrevoked: true. - Authority class is
governanceonly -- the named human project-governance authority for external environment/tool changes. A shape-validanalystordata_ownerrow is refused. - The decision must be COMMITTED.
seshat integrations setup --applyreads the file at HEAD, so an uncommitted transcription authorizes nothing -- which is the protection: the party requesting the install cannot also supply the permission.
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.
- 9d ago First seen · 256 lines · 48 tokens per session scan A b2506b591d11
approval-console is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 3,718 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.