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 skills add DangJin/bi-builder-skills --skill bi-buildergit clone --depth 1 https://github.com/DangJin/bi-builder-skillsWrote 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/dangjin/bi-builder-skills/bi-builder)<a href="https://agentmods.dev/skills/dangjin/bi-builder-skills/bi-builder"><img src="https://agentmods.dev/badge/skills/dangjin/bi-builder-skills/bi-builder/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/skills/dangjin/bi-builder-skills/bi-builder"><img src="https://agentmods.dev/badge/skills/dangjin/bi-builder-skills/bi-builder.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.00033 | $0.04841 |
| Opus 5 | $0.00016 | $0.02420 |
| Sonnet 5 | $0.00007 | $0.00968 |
| Haiku 4.5 | $0.00003 | $0.00484 |
Grade A, and why
bi-builder 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 10d 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 — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BI Builder
Build BI dashboards from existing databases, from data exploration to full implementation.
Tech Stack
| Layer | Technology |
|---|---|
| Frontend Framework | Next.js 16 (App Router) |
| UI Components | shadcn/ui + Tailwind CSS |
| Charts | Recharts |
| ORM | Prisma |
| Database | MySQL / PostgreSQL / Supabase / SQLite |
Core Workflow
Database Connection → Schema Exploration → Requirements Dialog → Metrics Design → Chart Planning → Page Implementation
Workflow Flexibility
Skip phases based on project state and user needs:
| Scenario | Skip Phases | Starting Point |
|---|---|---|
Project has prisma/schema.prisma |
Phase 1 | Go directly to Phase 2 schema analysis |
| User has clear requirements and metrics | Phase 3 | Go directly to Phase 4 metrics design |
| Only need a single chart component | Phases 1-5 | Read recharts-guide.md and implement |
| Only need data query logic | Phases 5-6 | End after metrics design |
Decision criteria:
- Check if
prisma/schema.prismaexists in project - Ask user "Do you have specific metrics requirements?"
- Ask user "Do you need a full dashboard or just a single chart?"
Phase 1: Database Connection
1.1 Check and Install Prisma
First, check if Prisma is already installed in the project:
# Check if prisma is in package.json dependencies
grep -q '"prisma"' package.json && echo "Prisma installed" || echo "Prisma not installed"
If Prisma is not installed, install it:
# Install Prisma as dev dependency
npm install prisma --save-dev
# Install Prisma Client
npm install @prisma/client
1.2 Initialize Prisma
# Initialize Prisma (creates prisma/schema.prisma and .env)
npx prisma init
Note: If prisma/schema.prisma already exists, skip this step.
1.3 Create .env with Placeholders
⚠️ Security Note: Never ask users to share database credentials directly.
First, ask user which database type they use, then create .env file with placeholders:
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 646 lines · 33 tokens per session scan A 60dc047a2ac2
bi-builder is a skill published in the GitHub repository DangJin/bi-builder-skills (2 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 4,841 once invoked, about $0.0002 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
nextjs-data-access-layer
Build secure, reusable data access patterns with DTOs, taint checks, and colocated authorization in Next.js. Use when centralizing database queries, transforming raw data to DTOs, adding server-only guards, or preventing sensitive data from reaching Client Components.
clone-production
Clone a production database with automatic PII anonymization.
migration-start
Begin a zero-downtime schema migration using pgroll.
branch-create
Create an isolated database branch for feature development.
setup
Connect this project to your Xata account, initialize pgroll and run migrations.
migration-complete
Finish an ongoing migration by running the contract phase.