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 commands/luccapinto/agentic-data-kit/document-dashboardgit clone --depth 1 https://github.com/luccapinto/agentic-data-kitWhat 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.00015 | $0.00341 |
| Opus 5 | $0.00008 | $0.00170 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
document-dashboard 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 2d 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
Workflow: /document-dashboard
Usage: /document-dashboard [path/to/project.pbip] [--output path/to/doc.md]
Builds a data catalog for a Power BI model by parsing the semantic model and report, removing
the need to hand-maintain dashboard documentation. Default output: DASHBOARD_DOC.md at the
project root.
Steps
- Inventory. Use
pbi-semantic-layer-tmdlto confirm the PBIP project and count tables, measures, relationships, pages, and visuals. - Parse both layers.
- Semantic model (
.tmdl): names, data types,description, DAXexpressions, and relationships fromrelationships.tmdl. - Report (
.json): scanpages/*/visuals/*/visual.jsonfor visual type, title, and the fields/measures used (projections).
- Semantic model (
- Generate. Follow the
documentation-templatesskill — itstemplates/powerbi-dashboard.md— to compile a Markdown doc with at least: overview, data dictionary, measure inventory (with DAX blocks), visual→measure→column map per page, and a relationships table. - Deliver. Save
DASHBOARD_DOC.md, then report its location and the documentation coverage (% of tables and measures with descriptions). If coverage < 80%, suggest running/validate-pbior offer to fill the gaps via TMDL.
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.
- 2d ago First seen · 29 lines · 15 tokens per session scan A 14e9331b71ce
document-dashboard is a command published in the GitHub repository luccapinto/agentic-data-kit (7 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 341 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-08-31.
Other commands, from other repositories
test-discovery
Discover and write missing tests for altimate-code. Runs hourly to find real-world gaps. Uses a team with a critic to validate tests before committing.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
choose-model
Compare current models across configured AI providers and produce an executable plan without running paid work. Use when the user asks which model or provider should perform a task.
setup
Check whether GitHub Copilot CLI is installed, authenticated, and ready for delegation.
review
Review code across five axes with categorized findings.
maintenance
Run routine maintenance on the AI knowledge base system.