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/bkper/bkper-cli/agents-mdgit clone --depth 1 https://github.com/bkper/bkper-cliWhat 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.02258 | $0.02258 |
| Opus 5 | $0.01129 | $0.01129 |
| Sonnet 5 | $0.00452 | $0.00452 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
bkper-cli 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 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Bkper CLI Development Guide
Overview
Bkper CLI is a command-line client for Bkper (financial accounting platform). The project uses TypeScript, Bun, Mocha for testing, and gts (Google TypeScript Setup) for code style enforcement.
README file
The README.md file is the main documentation for the project, its showed at github and npm, as well as serving as the content for the app listing on the Bkper website and main Dashboard. It should be kept up to date with the latest features and usage instructions, and should be clear and concise for users of all levels. In the high level it should be divided in a session user will see, and an expandable session for developers, more technical, with reference documentation and more detailed instructions. Its a public facing document, so it should be written for a general audience, with a focus on clarity and ease of use.
README restrictions
- NEVER add internal technical or SDLC workflow details to README.md
- NEVER document release labels, release automation, publishing policy, CI/CD flow, branch strategy, or maintainer-only procedures in README.md
- Keep maintainer and contributor workflow details in CONTRIBUTING.md, AGENTS.md, or internal docs instead
- If in doubt, prefer removing internal process detail from README.md rather than adding it
Build Commands
# Full build (clean, compile, copy assets)
bun run build
# Development with TypeScript watch
bun run dev
Note: The CLI builds worker bundles only (
bkper app build). Client tooling (Vite) is owned by the app template and configured viavite.config.ts. The template'snpm run devruns both Vite andbkper app devconcurrently, andnpm run buildruns bothvite buildandbkper app build.
Test Commands
# Run all tests
bun run test:all
# Run unit tests only
bun run test:unit
# Run integration tests only
bun run test:integration
# Run a single test file
TS_NODE_PROJECT=tsconfig.test.json npx mocha --config .mocharc.json test/unit/commands/apps/list.test.ts
# Run a single test (grep pattern)
TS_NODE_PROJECT=tsconfig.test.json npx mocha --config .mocharc.json --grep "should return proper" test/unit/**/*.test.ts
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 · 215 lines · 2,258 tokens per session scan A 997ac3c51a2c
bkper-cli AGENTS.md is an instructions file published in the GitHub repository bkper/bkper-cli (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 2,258 tokens to every session, about $0.0113 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
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.