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.
git 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/commands/kemetra/seshat-bi/dagster-evidence)<a href="https://agentmods.dev/commands/kemetra/seshat-bi/dagster-evidence"><img src="https://agentmods.dev/badge/commands/kemetra/seshat-bi/dagster-evidence/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/commands/kemetra/seshat-bi/dagster-evidence"><img src="https://agentmods.dev/badge/commands/kemetra/seshat-bi/dagster-evidence.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.00011 | $0.00155 |
| Opus 5 | $0.00005 | $0.00077 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
dagster-evidence 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 8d 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.
What it actually says
Load the dagster-workflows skill. Run seshat dagster evidence to list
recorded orchestration runs, or
seshat dagster evidence --run-id <id> to validate and render one run's
committed evidence markdown. The record is DERIVED evidence about an execution
(per-asset gate command, exit code, measured numbers, blocked/skipped reasons
with named owners) -- outcomes are execution words, never the readiness token
pass, and no numeric score exists anywhere in it. If rendering is refused
because the raw records fail schema validation, report the validation errors
verbatim; never hand-edit records to make them render.
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.
- 8d ago First seen · 14 lines · 11 tokens per session scan A c66ed633624d
dagster-evidence is a command published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 155 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
ADO: Get Build Info
Query Azure DevOps build pipeline status and failure details, optionally linking results to work items.
azure-graph-dotnet:deploy-azure
Deploy a C# Azure Functions or Container Job project to Azure — provision infrastructure with Bicep, push image to ACR, assign Managed Identity Graph permissions, and generate or update GitHub Actions or Azure DevOps CI/CD pipelines.
fix-failed-job
A command workflow for repairing a failed GitHub Actions job, which is an automated task run by GitHub for a software project.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.