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/readiness-viewer/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/readiness-viewer)<a href="https://agentmods.dev/skills/kemetra/seshat-bi/readiness-viewer"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/readiness-viewer/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/readiness-viewer"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/readiness-viewer.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.00187 | $0.03823 |
| Opus 5 | $0.00093 | $0.01912 |
| Sonnet 5 | $0.00037 | $0.00765 |
| Haiku 4.5 | $0.00019 | $0.00382 |
Grade A, and why
readiness-viewer 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 10d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
readiness-viewer
The F012 control room answers "what is broken, how badly, worst-first". The Readiness Viewer answers a different question over the SAME inputs: "which of the seven stages has each item reached, with what evidence, and who approved the gate that let it advance". It is a read-only stage-progression LENS over evidence that already exists per item -- it introduces no new validator and no new gate (roadmap rule #8; Principle VIII). It renders, then STOPS.
Module contract (this skill IS a filled Product Module declaration)
This skill declares its authority category up front, per the F024 Companion Tools
Architecture contract (templates/module-contract.md).
- Authority category: Product Module
- Capability level:
read-only(exactly one) - Product layer:
4(the functional axis -- see docs/roadmap/roadmap.md; orthogonal to category; matches the F012 control-room sibling) - Roadmap feature:
F026On-disk spec:specs/020-readiness-viewer/(roadmap F-number is authoritative when the two disagree) - Owner:
the readiness / data-quality lead(a named role -- never "the agent") - Status:
Authored
What it does (one line)
Reads each item's
readiness-status.yaml(Core Authority) and presents the seven-stage status matrix, each stage'sevidence[]as navigable references, and theapprovals[]timeline -- creating no truth.
Core Authority it READS
It reads these committed truth artifacts; it never writes them.
mappings/<item>/readiness-status.yaml--current_stage, per-stagestatus(the four words),evidence[],blocking_reasons[],approvals[],next_action.- the files each
evidence[]entry references (to mark a reference "referenced file not found" when absent -- it reads them only to check existence, never edits). - the "Required owner / approval" field of each
docs/readiness/<stage>-ready.md(to know which gates require an approval before flagging a missing one).
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.
- 10d ago First seen · 276 lines · 187 tokens per session scan A 85e61ec8e0a9
readiness-viewer is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 187 tokens to every session and 3,823 once invoked, about $0.0009 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.