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/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/mcp/proompteng/bilig/biligworkpaperfile)<a href="https://agentmods.dev/mcp/proompteng/bilig/biligworkpaperfile"><img src="https://agentmods.dev/badge/mcp/proompteng/bilig/biligworkpaperfile/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/mcp/proompteng/bilig/biligworkpaperfile"><img src="https://agentmods.dev/badge/mcp/proompteng/bilig/biligworkpaperfile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
biligWorkpaperFile 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 yesterday.
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
{
"biligWorkpaperFile": {
"type": "stdio",
"command": "npm",
"args": [
"exec",
"--yes",
"--package",
"@bilig/workpaper@latest",
"--",
"bilig-workpaper-mcp",
"--workpaper",
"./.bilig/pricing.workpaper.json",
"--init-demo-workpaper",
"--writable"
],
"env": {}
}
}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.
- yesterday First seen · 19 lines scan A 1ff1c1d36256
biligWorkpaperFile is an MCP server published in the GitHub repository proompteng/bilig (36 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-07.
Other mcp servers, from other repositories
mcp-server-excel
MCP server "mcp-server-excel" as configured in sbroenne/mcp-server-excel. Launched with Sbroenne.ExcelMcp.McpServer.
anytype-mcp
Official MCP server for Anytype API - your encrypted, local and collaborative wiki. Runs locally from the @anyproto/anytype-mcp npm package. Needs 1 environment variable to run.
mcp-documentation-server
Local-first document management and semantic search for AI coding agents. Runs locally from the @andrea9293/mcp-documentation-server npm package.
adeu
MCP server "adeu" as configured in dealfluence/adeu. Runs locally from the adeu-server Python package.
mcp-outline
A Model Context Protocol (MCP) server for Outline (https://www.getoutline.com). Runs locally from the mcp-outline Python package. Needs 6 environment variables to run.
nutrient-document-engine-mcp-server
MCP server for self-hosted Nutrient Document Engine: extract, edit, redact, and annotate documents. Runs locally from the @nutrient-sdk/document-engine-mcp-server npm package. Needs 5 environment variables to run.