Borrowing it
Nothing to install: this file belongs to kirill-markin/expense-budget-tracker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kirill-markin/expense-budget-tracker/main/AGENTS.mdgit clone --depth 1 https://github.com/kirill-markin/expense-budget-trackerWrote 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/kirill-markin/expense-budget-tracker/agents-md)<a href="https://agentmods.dev/instructions/kirill-markin/expense-budget-tracker/agents-md"><img src="https://agentmods.dev/badge/instructions/kirill-markin/expense-budget-tracker/agents-md.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.1 | $0.02391 | $0.02391 |
| Opus 5 | $0.01196 | $0.01196 |
| Sonnet 5 | $0.00478 | $0.00478 |
| Haiku 4.5 | $0.00239 | $0.00239 |
Grade A, and why
expense-budget-tracker 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 8d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expense-budget-tracker
Open-source expense and budget tracker: expenses, budgets, balances, transfers, and multi-currency reporting on Postgres.
Rules
- Use English for code comments and documentation.
- Prefer functional programming and pure functions.
- Use classes only for connectors to external systems.
- Use strict typing across functions, variables, and collections.
- Avoid fallback logic unless explicitly requested.
- Raise explicit, actionable errors with context.
- Runtime discovery is the canonical machine API documentation. Keep its actions, instructions, and source links in sync with runtime behavior;
/v1/openapi.jsonand/v1/swagger.jsonare public source-discovery compatibility probes, not specification endpoints. - Version-bump requests must follow
docs/version-bump.mdand keepscripts/checks/pr/check-version-alignment.mjsgreen. - Keep changes minimal and scoped to the current request.
- Before considering a large block of work complete, run the relevant type checks and builds, and for web changes a production build (
cd apps/web && npm run lint && npm run build). - Prefer non-interactive terminal commands.
- The web app supports multiple languages. When adding or changing any translation in
apps/web/src/i18n/, update the same keys in every locale file in that directory in the same change. - Change schema via new files in
db/migrations/only; never edit already-applied migrations. - CI/CD is GitHub Actions on push to
main(.github/workflows/deploy.yml). - The deploy process intentionally may update the web service before running migrations; this accepted deploy order is not an issue by itself.
- Do not build AWS SDK bundles or other AWS deployment artifacts locally. Push code to
main, and let CI/CD build and deploy everything. - RTL support is required:
- In CSS, use logical properties such as
inset-inline-start/end,margin-inline-start/end,padding-inline-start/end,border-inline-start/end, andtext-align: start/endinstead of physical left/right variants. - Use
[dir="rtl"]overrides only when no logical equivalent exists (for examplebox-shadow). - In JS, account for RTL when handling
scrollLeft, element positioning, and resize logic.
- In CSS, use logical properties such as
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.
- 8d ago First seen · 134 lines · 2,391 tokens per session scan A a122e2936d9c
expense-budget-tracker AGENTS.md is an instructions file published in the GitHub repository kirill-markin/expense-budget-tracker (30 stars, last pushed 6d ago), licensed MIT. It adds 2,391 tokens to every session, about $0.0120 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
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.
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.
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).
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).
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.
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.