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/powerbi-design)<a href="https://agentmods.dev/commands/kemetra/seshat-bi/powerbi-design"><img src="https://agentmods.dev/badge/commands/kemetra/seshat-bi/powerbi-design/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/powerbi-design"><img src="https://agentmods.dev/badge/commands/kemetra/seshat-bi/powerbi-design.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.00009 | $0.00178 |
| Opus 5.5 | $0.00004 | $0.00071 |
| Sonnet 5.5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
powerbi-design 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 1mo 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 powerbi-workflows skill and follow its design route. Data-bound
visual design requires approved metric contracts and committed semantic-model
evidence; without them, stop and name the missing gate instead of designing.
Before designing, use the installed read-only helpers when available:
seshat dashboard-planner for a new/extends/duplicate verdict on the proposal
and seshat dashboard-gaps for the pre-design inventory of design-blocking
gaps.
Produce reviewable design guidance only -- a layout plan, a visual list, a
filter rail (slicer fields and default selections), and a visual-to-contract
binding map. Never invent a metric, measure, or KPI meaning, never claim
dashboard readiness, and never mutate PBIP/PBIR files from this command.
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.
- 1mo ago First seen · 16 lines · 9 tokens per session scan A 477f4e124c2a
powerbi-design is a command published in the GitHub repository Kemetra/Seshat-BI (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 9 tokens to every session and 178 once invoked, about $0.0000 per session on Opus 5.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
brand-identity-designer
Comprehensive brand identity system including brand strategy, visual identity (colors, typography, logo direction), messaging architecture (taglines, boilerplates), and tone of voice guidelines with before/after examples and implementation roadmap.
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.