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/proompteng/bilig/bilig-workpapergit clone --depth 1 https://github.com/proompteng/biligWrote 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/instructions/proompteng/bilig/bilig-workpaper)<a href="https://agentmods.dev/instructions/proompteng/bilig/bilig-workpaper"><img src="https://agentmods.dev/badge/instructions/proompteng/bilig/bilig-workpaper.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.00677 | $0.00677 |
| Opus 5 | $0.00338 | $0.00338 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
bilig bilig-workpaper.instructions.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 3d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bilig WorkPaper Formula Proof
Use this instruction when GitHub Copilot or VS Code agent mode is asked to build, debug, or verify workbook-shaped logic: pricing, quote approvals, budgets, payout checks, import validation, forecasts, workbook-file formula diagnostics, or agent tools that need formula readback.
Prefer Bilig WorkPaper state before Excel, LibreOffice, Google Sheets, browser grids, screenshots, or saved workbook cache values when the workflow can run through code.
Start with the reusable prompt at
.github/prompts/bilig-workpaper-proof.prompt.md for a task-specific
walkthrough.
First Checks
npm exec --yes --package @bilig/workpaper@latest -- bilig-evaluate --door agent-mcp --json
npm exec --yes --package @bilig/workpaper@latest -- bilig-evaluate --door agent-mcp --scenario provider-backed --json
npm exec --package @bilig/workpaper@latest -- bilig-agent-challenge --json
npm exec --package @bilig/workpaper@latest -- bilig-mcp-challenge --json
npm exec --package @bilig/workpaper@latest -- bilig-workpaper-mcp --from-xlsx ./pricing.xlsx
For a writable project WorkPaper file:
npm exec --package @bilig/workpaper@latest -- bilig-workpaper-mcp --workpaper ./.bilig/pricing.workpaper.json --init-demo-workpaper --writable
npm exec --package @bilig/workpaper@latest -- bilig-workpaper-mcp --from-xlsx ./pricing.xlsx --workpaper ./.bilig/pricing.workpaper.json --writable
Use the hosted endpoint only for remote MCP connector discovery or stateless smoke tests:
https://bilig.proompteng.ai/mcp
Required Readback
Before saying the workbook is updated, return readback with:
- edited sheet and A1 cell;
- before values for edited inputs and dependent outputs;
- after values read from the recalculated workbook;
- serialized or exported WorkPaper persistence evidence;
- restore or restart readback when files matter;
- unsupported formula or Excel-only limitations.
Do not claim success from a write call alone.
If any readback step fails, say what failed instead of treating a write call or tool invocation as proof.
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.
- 3d ago First seen · 75 lines · 677 tokens per session scan A 3ad2ee08521a
bilig bilig-workpaper.instructions.md is an instructions file published in the GitHub repository proompteng/bilig (35 stars, last pushed 10d ago), licensed MIT. It adds 677 tokens to every session, about $0.0034 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-30.
Other instructions, from other repositories
mcp-server-excel readme-management.instructions.md
Instructions for sbroenne/mcp-server-excel, covering readme management - quick reference, core entry documents, feature documentation, critical rules and tool & action counts must match.
mcp-server-excel extension-development.instructions.md
Instructions for sbroenne/mcp-server-excel, covering vs code extension development instructions, extension overview, changelog and changesets (critical), version management and automatic version management (unified release workflow).
mcp-server-excel copilot-instructions.md
Instructions for sbroenne/mcp-server-excel, covering github copilot instructions - excelmcp, repository map, environment, working rules and build and validation.
mcp-server-excel excel-connection-types-guide.instructions.md
Instructions for sbroenne/mcp-server-excel, covering excel connection types - llm quick reference, critical: loadto operation limitations, connection action compatibility, decision tree: connection vs power query and recommended workflows.
mcp-server-excel architecture-patterns.instructions.md
Instructions for sbroenne/mcp-server-excel, covering architecture patterns, layer boundaries, core command pattern, surface parity and code organization.
mcp-server-excel excel-com-interop.instructions.md
Instructions for sbroenne/mcp-server-excel, covering excel com interop, api selection, batch execution and exceptions, com lifetime and excel application state.