Borrowing it
Nothing to install: this file belongs to matiasbattocchia/open-bsp-api. 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/matiasbattocchia/open-bsp-api/main/CLAUDE.mdgit clone --depth 1 https://github.com/matiasbattocchia/open-bsp-apiWrote 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/matiasbattocchia/open-bsp-api/claude-md)<a href="https://agentmods.dev/instructions/matiasbattocchia/open-bsp-api/claude-md"><img src="https://agentmods.dev/badge/instructions/matiasbattocchia/open-bsp-api/claude-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.01481 | $0.01481 |
| Opus 5 | $0.00740 | $0.00740 |
| Sonnet 5 | $0.00296 | $0.00296 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
open-bsp-api CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.supabase.com/v1/projects/${REF}/analytics/endpoints/logs.all" \ How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project overview
Open BSP API — a multi-tenant WhatsApp Business Platform integration built with Deno, Postgres, and Supabase Edge Functions. See README.md for full details.
Local checks must match CI (deno)
CI (.github/workflows/check.yml) runs:
deno fmt --check
cd supabase/functions && deno lint && deno check .
cd plugin && deno lint && deno check .
deno check only works from inside the package dir. Run
cd supabase/functions && deno check . — NOT deno check <file> from the repo
root. The import map lives in supabase/functions/deno.json (there is no root
deno.json), so checking a file from the root resolves no bare specifiers and
prints false Import "@supabase/supabase-js" not a dependency /
"ky"/"zod"/"postgres" errors. These are an artifact of the wrong CWD, not
real errors — don't treat them as a pre-existing baseline.
The
.claude/settings.jsonPostToolUse hook runsdeno check <file>withoutcdand swallows output with|| true, so it always "passes" for functions files and verifies nothing there. Run the CI command yourself to actually verify.
deno fmt output is deno-version-dependent. The repo pins fmt config
(lineWidth 80, semicolons, double quotes) but not the deno binary (CI uses
v2.x). A different local deno can report spurious diffs on generated files
(e.g. _shared/db_types.ts). Only format files you actually changed; never
reformat the whole tree to chase a version-difference diff.
Debugging production edge functions
Timestamps
The current date/time is NOT reliably in the conversation context. When querying
logs with time ranges (e.g., "last 12 hours"), always run date -u first to
get the actual current UTC time. Do not guess or hardcode timestamps.
Querying stdout logs (console.log / console.error)
Use the Supabase Management API to query function_logs (edge function stdout):
ACCESS_TOKEN=$(cat ~/.supabase/access-token)
REF="nheelwshzbgenpavwhcy"
curl -s "https://api.supabase.com/v1/projects/${REF}/analytics/endpoints/logs.all" \
-H "Authorization: Bearer ${ACCESS_TOKEN}" \
-G \
--data-urlencode "sql=select cast(timestamp as datetime) as ts, event_message from function_logs where regexp_contains(event_message, 'ERROR_KEYWORD') order by timestamp desc limit 10" \
--data-urlencode "iso_timestamp_start=2026-04-10T00:00:00Z"
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 · 136 lines · 1,481 tokens per session scan A 2b427f79962b
open-bsp-api CLAUDE.md is an instructions file published in the GitHub repository matiasbattocchia/open-bsp-api (569 stars, last pushed 8d ago), licensed Unlicense. It adds 1,481 tokens to every session, about $0.0074 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.