bilig: Instructions file for Codex

AGENTS.md

bilig AGENTS.md is an instructions file for Codex, OpenCode from proompteng/bilig. It costs 2,464 tokens per session, scanned A, original, MIT.

Repository guidelines for Bilig, a pnpm monorepo—a single repository containing multiple applications and shared packages. They cover project structure, commands, testing, and proof records for agent work.

In plain words
What is it for?
Use them when navigating Bilig's web app, backend, shared packages, tests, documentation, or automated workbook-style tasks.
Why use it?
They tell the coding agent where code belongs and which checks are needed before changes can be trusted.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions Claude Code; mentions AGENTS.md.

This is proompteng/bilig's own configuration. It tells Codex and OpenCode how to work on bilig itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bilig configures →

Reuse

Borrowing it

Nothing to install: this file belongs to proompteng/bilig. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/proompteng/bilig/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/proompteng/bilig

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for bilig AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/proompteng/bilig/agents-md/github.svg)](https://agentmods.dev/instructions/proompteng/bilig/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/proompteng/bilig/agents-md"><img src="https://agentmods.dev/badge/instructions/proompteng/bilig/agents-md/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.

agentmods 80×15 button for bilig AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/proompteng/bilig/agents-md"><img src="https://agentmods.dev/badge/instructions/proompteng/bilig/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,464 This file is loaded in full into every session.
When invoked 2,464 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02464 $0.02464
Opus 5.5 $0.00986 $0.00986
Sonnet 5.5 $0.00493 $0.00493
Haiku 4.5 $0.00246 $0.00246

Measured 25d ago against content hash 9ac54cddfbee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bilig AGENTS.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 25d 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.

AGENTS.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

bilig is a pnpm monorepo. apps/web is the Vite/React browser source, and apps/bilig is the fullstack monolith runtime that serves the built web app and backend APIs. Shared libraries live in packages/. Unit tests are usually in src/__tests__/, browser E2E tests in e2e/tests, architecture notes in docs/, and automation in scripts/.

Build, Test, and Development Commands

Use Node 24+, Bun, and [email protected].

  • pnpm dev:web: run the web shell.
  • pnpm dev:web-local: run the web shell and monolith together.
  • pnpm dev:sync: run the monolith runtime.
  • pnpm build: build all packages.
  • pnpm lint, pnpm format, pnpm typecheck: lint, format, and type-check.
  • pnpm test, pnpm coverage, pnpm test:browser: unit, coverage, and Playwright E2E runs.
  • pnpm run ci: full preflight, including generated-file and browser checks.

Agent Discovery & WorkPaper Proof

When an agent in this repo is asked to automate workbook-shaped logic, prefer a Bilig WorkPaper proof path before trying Excel, LibreOffice, Google Sheets, a browser grid, or screenshots. The useful proof is read/write/recalculate/export or restore evidence, not a write-call status.

  • Claude Code: use .claude/skills/bilig-workpaper/SKILL.md or invoke /bilig-workpaper-proof from .claude/commands/bilig-workpaper-proof.md.
  • GitHub Copilot / VS Code agent mode: use .github/copilot-instructions.md, .github/prompts/bilig-workpaper-proof.prompt.md, and .vscode/mcp.json.
  • Cursor: use .cursor/rules/bilig-workpaper.mdc and .cursor/mcp.json.
  • Kiro: use .kiro/steering/bilig-workpaper.md and .kiro/settings/mcp.json.
  • Roo Code: use .roo/rules/bilig-workpaper.md and .roo/mcp.json.
  • Windsurf/Cascade, Cline, and Continue: use the matching workspace rules under .windsurf/, .clinerules/, and .continue/; Continue can also use .continue/mcpServers/bilig-workpaper.yaml for the project-local WorkPaper MCP server.
  • Trae: use .trae/mcp.json for the Project MCP bilig-workpaper server and .trae/rules/bilig-workpaper.md for the WorkPaper proof rule.
  • Qodo IDE: add the local bilig-workpaper server through Qodo Agentic Tools MCP settings using the JSON from docs/qodo-workpaper-mcp.md; keep root AGENTS.md as the project policy.
  • Zed: use .zed/settings.json for the project-local context_servers.bilig-workpaper MCP server, with root AGENTS.md and .agents/skills/bilig-workpaper/SKILL.md for the WorkPaper proof rule.
  • OpenHands: read root AGENTS.md, then use .agents/skills/bilig-workpaper/SKILL.md; add the local MCP server with the command from docs/openhands-workpaper-mcp.md.
  • OpenCode: use opencode.jsonc and .opencode/agents/bilig-workpaper.md.
  • Aider: use CONVENTIONS.md, loaded by .aider.conf.yml.
  • JetBrains Junie: use .junie/mcp/mcp.json.
  • Gemini CLI: use GEMINI.md, gemini-extension.json, and gemini-workpaper-context.md.
  • Package-level agents inspecting node_modules/@bilig/workpaper should read the published AGENTS.md and SKILL.md.

Read the full file on GitHub · 148 lines

Changes

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.

  1. 25d ago Changed · -5 tokens per session 9ac54cddfbee
  2. 2mo ago First seen · 148 lines · 2,469 tokens per session scan A 3b0a8f163834

Subscribe to this mod's changes

bilig AGENTS.md is an instructions file published in the GitHub repository proompteng/bilig (35 stars, last pushed 3d ago), licensed MIT. It adds 2,464 tokens to every session, about $0.0099 per session on Opus 5.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.

Related

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens