Borrowing it
Nothing to install: this file belongs to cammac-creator/ibanforge. 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/cammac-creator/ibanforge/main/AGENTS.mdgit clone --depth 1 https://github.com/cammac-creator/ibanforgeWrote 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/cammac-creator/ibanforge/agents-md)<a href="https://agentmods.dev/instructions/cammac-creator/ibanforge/agents-md"><img src="https://agentmods.dev/badge/instructions/cammac-creator/ibanforge/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.
<a href="https://agentmods.dev/instructions/cammac-creator/ibanforge/agents-md"><img src="https://agentmods.dev/badge/instructions/cammac-creator/ibanforge/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.06205 | $0.06205 |
| Opus 5.5 | $0.02482 | $0.02482 |
| Sonnet 5.5 | $0.01241 | $0.01241 |
| Haiku 4.5 | $0.00620 | $0.00620 |
Grade A, and why
ibanforge 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 today.
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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on IBANforge
Instructions for any coding agent opening this repository. Codex reads this file;
Claude Code reads CLAUDE.md next to it. The two must say the same thing — if you
change a rule here, change it there.
docs/handover.md is the long version: why each rule below exists, how the bank-code
verdict works, what a green test suite does not prove, the traps already paid for, the work
in flight and the known debts. Read this file first, that one before your first commit.
IBANforge is an IBAN validation and BIC lookup API. Three areas live in one repository:
| Area | Path | Runs on | Deployed by |
|---|---|---|---|
| The API (Hono, TypeScript, SQLite) | src/, scripts/, data/ |
Node 22 | Railway, on every push to main |
| The website and dashboard (Next.js) | frontend/ |
Node 24 | a container image built by .github/workflows/deploy-site.yml, run on an Infomaniak server in Switzerland (see below) |
| The published packages | mcp/, sdks/, integrations/ |
Node 20 | a tagged release workflow, never by hand |
The rules that are not negotiable
1. Never push to main. A push to main deploys the API to production. There is no
staging. Work on a branch, open a pull request, let CI go green, and let a human merge.
main carries a ruleset that forbids force-push and deletion (since 2026), but it requires no pull
request and no review: for everything else, the rule is the protection.
2. This repository is public. Never write a customer's or prospect's name, a real
e-mail address, or a real activity figure (accounts, calls served, revenue, reply rates)
into code, comments, test fixtures, documentation or commit messages. A pushed commit
message cannot be rewritten. Invented fixtures only: [email protected], Société Alpha,
alpha.example.net. Public bank names and public bank codes are data, and are fine.
The reasoning stays, the quantity goes: "measured on the real mailbox, N of M were bots"
becomes "close to a third were automation".
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.
- today Changed · +21 tokens per session 9ce1af2fd563
- yesterday Changed · +32 lines · +716 tokens per session 18181d550ce7
- 4d ago Changed · +4 lines · +92 tokens per session a7fba8eca432
- 5d ago Changed · +3 lines · +55 tokens per session 521f968bcc2a
- 9d ago Changed · +16 lines · +385 tokens per session eefde00ac5c6
- 23d ago Changed · +4 lines · +106 tokens per session 40425505629d
- 24d ago Changed · +11 lines · +268 tokens per session 9f199b593223
- 1mo ago Changed · +3 lines · +70 tokens per session d0380c60af59
- 1mo ago Changed · +5 lines · +128 tokens per session 24bb1aa1df04
- 1mo ago First seen · 275 lines · 4,364 tokens per session scan A 11e4c64a5fa0
ibanforge AGENTS.md is an instructions file published in the GitHub repository cammac-creator/ibanforge (3 stars, last pushed yesterday), licensed MIT. It adds 6,205 tokens to every session, about $0.0248 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-09-11.
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).
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.
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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.