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/run-next-readiness/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/run-next-readiness)<a href="https://agentmods.dev/skills/kemetra/seshat-bi/run-next-readiness"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/run-next-readiness/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/run-next-readiness"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/run-next-readiness.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.00060 | $0.03911 |
| Opus 5 | $0.00030 | $0.01956 |
| Sonnet 5 | $0.00012 | $0.00782 |
| Haiku 4.5 | $0.00006 | $0.00391 |
Grade A, and why
run-next-readiness 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
run-next-readiness
retail-orchestrate observes disk state, decides the next phase, and then
EXECUTES it (self-healing against the gate). This skill is the extracted,
standalone, READ-ONLY decision half: given ONE table's committed
readiness-status.yaml, it computes the single next allowed action and STOPS.
It runs nothing, writes nothing, and grants nothing. It answers the question;
the human (or retail-orchestrate) acts on the answer.
Module contract (this skill IS a filled Product Module declaration)
Per the F024 Companion Tools Architecture contract (templates/module-contract.md).
- Authority category: Product Module
- Capability level:
read-only(exactly one) - Product layer:
4(readiness spine lens; orthogonal to category) - Roadmap feature:
F080On-disk spec:specs/080-run-next-readiness-state-machine/ - Owner:
the readiness / data-quality lead(a named role -- never "the agent") - Status:
Authored
What it does (one line)
Reads one table's
readiness-status.yaml(Core Authority), walks the seven stages in fixed order, and returns the single next allowed action (or a stop / approval-required / terminal / defect outcome) -- creating no truth, executing nothing.
Core Authority it READS
It reads these committed truth artifacts; it never writes them.
mappings/<table>/readiness-status.yaml--table,current_stage, per-stagestatus(the four words),evidence[],blocking_reasons[],approvals[],next_action. Its ABSENCE is a valid, handled case (not an error).- the "Next allowed action" and "Required owner / approval" fields of each
docs/readiness/<stage>-ready.md-- fixed reference vocabulary for phrasing the forward action and confirming which stages require an approval.
What it WRITES
Nothing. Its output is an ephemeral response to the caller (an agent turn, a
human, a future retail-orchestrate wiring), never a file on disk. The
read-only proof is git status --short empty after any invocation (SC-003).
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 · 295 lines · 60 tokens per session scan A 57fc2b68a1d0
run-next-readiness is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 3,911 once invoked, about $0.0003 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
powerbi-project-management
Project management for BI projects. Use when the user mentions: project plan, sprint, milestone, delivery, roadmap, stakeholder, requirements, scope, backlog, user story, epic, data product, product management, agile, kanban, release plan, go-live, risk, RAID log, data platform delivery, data project, BI delivery…
status-truth
Use when work is leaving the desk — findings, a status, or a number that must hold up in the room. The state of the WORK itself is being reported - a status report or weekly/steering update - and the truth must survive the pull to look green: every claim carries provenance, every green names what would turn it red…
jira_to_bi_spec
Skill "jira_to_bi_spec" from G-Schumacher44/strata-oss, covering skill: jiratobispec, trigger, inputs, allowed tools and forbidden.
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.