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.
npx agentmods add skills/kemetra/seshat-bi/source-mappingnpx skills add Kemetra/Seshat-BI --skill source-mappinggit 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/source-mapping)<a href="https://agentmods.dev/skills/kemetra/seshat-bi/source-mapping"><img src="https://agentmods.dev/badge/skills/kemetra/seshat-bi/source-mapping.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 | $0.00122 | $0.02762 |
| Opus 5 | $0.00061 | $0.01381 |
| Sonnet 5 | $0.00024 | $0.00552 |
| Haiku 4.5 | $0.00012 | $0.00276 |
Grade A, and why
source-mapping 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-mapping
The source-mapping gate is the kit's one load-bearing rule (constitution
Principle IV): before any silver.* SQL is written, the source MUST be
profiled and mapped into committed, reviewed artifacts. This skill runs that
gate: profile -> author the five artifacts -> stop at judgment calls -> hard-stop
before silver. It formalizes Phases 1-4 of the medallion playbook; the
playbook stays authoritative on HOW to decide, the templates on WHAT to record.
Scope boundary (read first)
This skill profiles a source and authors the mapping artifacts, then STOPS. It
does NOT write silver.* or gold.* SQL, does NOT call pbi-cli or Power BI
Desktop, and does NOT decide the judgment calls Principle V reserves for a human.
Silver is downstream of an APPROVED map -- approval is the reviewer's action, not
this skill's.
The five artifacts (write the blanks with seshat scaffold-source <table>)
Run seshat scaffold-source <table> to materialize the canonical blanks into
mappings/<table>/. Do NOT hand-author these files, and do NOT copy from a
templates/ path: templates/ exists only in the Seshat development repo, so
that instruction fails for anyone who installed the kit as a tool -- and a
hand-written source-map.yaml silently misses the canonical shape that
seshat validate and the gold stages require (issue #488). The scaffolder ships
inside the package and never overwrites an existing file.
Per ADR 0003 (mapping-artifact location), a
table's filled set lives in mappings/<table>/:
source-profile.md-- Phase 1 numbers (this skill fills the mechanical ones).source-map.yaml-- the machine-readable spine (grain+PK first, per-column keep/drop/rename/type/PII/gold-placement, the gold star, derived columns).assumptions.md-- which RC1-RC16 defaults were ADOPTED vs DEVIATED (each deviation cites its triggering data fact).unresolved-questions.md-- the build-blocking judgment calls + who answers.reconciliation-report.md-- the blank the later live run fills (RC16).
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 · 194 lines · 122 tokens per session scan A a2ae8dcf5ccb
source-mapping is a skill published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 122 tokens to every session and 2,762 once invoked, about $0.0006 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
sl
Skill "sl" from Kaelio/ktx, covering semantic layer, part 1 - schema reference, overlay sources, standalone table sources and standalone sql sources.
historic_sql_patterns
Identify recurring cross-table historic-SQL analytical intents from a bounded pattern shard and emit typed pattern evidence for deterministic wiki projection.
historic_sql_table_digest
Convert one changed historic-SQL table usage bucket into typed table usage evidence for deterministic schema projection.
live_database_ingest
Capture semantic-layer and knowledge updates from a live database schema snapshot.
ktx
Installs and configures ktx, the open-source context layer for data agents — runs ktx setup non-interactively with hidden CLI flags, configures database connections and embeddings, installs agent integration, and verifies readiness. Use when the user asks an agent to add ktx to a project, connect data sources, install…
powerbi-source-integration
Source system integration patterns. Use when the user mentions: data source, connect source, ingest data, database connection, API connection, CSV upload, web scrape, source connector, raw data model, normalize, Bronze ingestion, source mapping, data model development, source to Bronze, multi-source, PostgreSQL…