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 instructions/twilize5/reportforge/claude-mdgit clone --depth 1 https://github.com/twilize5/reportforgeWhat 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.00551 | $0.00551 |
| Opus 5 | $0.00275 | $0.00275 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
reportforge 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 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ReportForge PBI
ReportForge PBI is a local-first Claude Desktop MCP app for generating Power BI
.pbit reports.
Supported Setup
Railway deployment is not the current target. The intended workflow is:
- Clone or download this repo locally.
- Run
setup_local.ps1. - Configure Claude Desktop to launch
run_mcp_stdio.ps1. - Use Claude Desktop MCP tools to read local CSV files and save reports locally.
Capabilities
- Generate Power BI dashboards from local CSV files.
- Generate from pasted CSV text or base64 CSV.
- Profile CSVs for measures, dimensions, temporal columns, geographic columns, KPI candidates, and domain hints.
- Build semantic model JSON, Power Query M, Power BI layout JSON, theme JSON,
and compiled
.pbitfiles. - Export local
.pbitfiles intogenerated_reports/. - Shorten generated filenames to avoid Windows/Power BI path errors.
- Apply template-based dashboard layouts:
- KPI rail
- KPI grid
- central chart slots
- right-side filter panel
- light canvas
- white cards
- subtle borders
- capped visual counts to avoid clutter
- Strip problematic generated sort metadata that caused Power BI Desktop 2026 renderer failures.
- Do not emit
hasDefaultSort,OrderBy,Sort, orsortDefinitionsin generated visual configs.
Anthropic API Usage
No Anthropic key is required for deterministic CSV-to-dashboard tools:
create_dashboardcreate_from_csv_file_pathcreate_from_csv_textcreate_from_csvexport_pbit_fileget_report_state
An Anthropic key is required for server-side LLM features:
create_reportadd_visualedit_stylingapply_image_themeadd_filter
In Claude Desktop local mode, put ANTHROPIC_API_KEY in the MCP server env
block or set it as a normal Windows environment variable.
Important Files
LOCAL_SETUP.md- complete local install and Claude Desktop config.setup_local.ps1- creates venv and installs Python requirements.run_mcp_stdio.ps1- Claude Desktop stdio entrypoint.run_api.ps1- optional local FastAPI entrypoint.mcp_server.py- MCP tool definitions.auto_intent.py- deterministic CSV dashboard generation.file_writer.py- Power BI project and PBIT writer.prompts/- prompt files for Anthropic-powered features.
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 · 71 lines · 551 tokens per session scan A 2d451dbaa59f
reportforge CLAUDE.md is an instructions file published in the GitHub repository twilize5/reportforge (0 stars, last pushed 2mo ago), licensed MIT. It adds 551 tokens to every session, about $0.0028 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 instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.