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.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/instructions/kemetra/seshat-bi/claude-md)<a href="https://agentmods.dev/instructions/kemetra/seshat-bi/claude-md"><img src="https://agentmods.dev/badge/instructions/kemetra/seshat-bi/claude-md.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.00835 | $0.00835 |
| Opus 5 | $0.00417 | $0.00417 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
Seshat-BI CLAUDE.md 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 4d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Seshat BI
Repo-specific rules. Global rules in ~/.claude/CLAUDE.md still apply.
What this repo is
A standalone analytics service — NOT bound by the Retail Tower OS
orchestrator / contract-boundary rules. Power BI primary; DigitalOcean Postgres
source. Data flows bronze → silver → gold; Power BI reads the gold
schema only.
For new retail mart work, start from a filled worked example under docs/worked-examples/ and follow the medallion playbook.
Hard rules
- Secrets: credentials only in
.env(git-ignored). Never write real values into tracked files. Power BI uses parameters, not baked-in connection strings. - PBIP
.gitignorebaseline is exact:**/.pbi/localSettings.jsonand**/.pbi/cache.abf. Never ignoredefinition/folders — that's the model. - PBIP is a preview feature (as of 2025-12); enable it in Power BI Desktop.
- Windows 260-char path limit — keep PBIP project/table names short.
- Line endings:
core.autocrlf=true; rely on.gitattributes. Edit PBIP text externally only as UTF-8 without BOM.
Conventions
SQL: snake_case; schemas bronze/silver/gold; vw_/fct_/dim_ prefixes;
numbered idempotent migrations. DAX: PascalCase measures in display folders. Full
detail in docs/conventions.md.
Scope discipline (YAGNI)
No live DB provisioning, no automated ingestion code, no orchestrator integration unless explicitly requested. Add the seam, not the implementation.
No active Spec Kit implementation plan.
Seshat BI kit router (v0.2.0) -- generated from .seshat/kit-source.yaml; do not edit here.
Orient first: What readiness stage am I serving? State lives in readiness-status.yaml (per TABLE, recomputed) (recomputed; this file stores none).
Verbs the agent drives:
retail-orchestrate-- conductor -- sequence the medallion verbs, self-heal against the gatefirst-hour-compass-- first-arrival worked-example offer + single-source seam list + single-table orientation cardretail-onboard-table-- Source->Mapping front door; owns the Stage-1 read-only DB-backed profile (grain candidates, column types)retail-discover-portfolio-- metadata-only portfolio discovery -> governed domain/scope proposals -> selected-table onboarding -> interview handoffbusiness-knowledge-interview-- after DB discovery, interview the owner into the Decision Store (batch low-risk, explicit critical); records decisions, never self-grants approvalsource-mapping-- the mapping gate -- produces source-map.yamlkpi-contract-builder-- drive the shipped kpi_contracts engine: assess answerability, list the decisions to approve, preview with per-field provenance, then draft/finalize -- never self-grants approvalretail-build-warehouse-- author silver/gold SQL; stop before executingretail-validate-- live checks; needs db extra + DSN, else [PENDING LIVE PROFILE]retail-govern-- static check (seshat check)
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.
- 4d ago First seen · 62 lines · 835 tokens per session scan A 325acb39895c
Seshat-BI CLAUDE.md is an instructions file published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 835 tokens to every session, about $0.0042 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.