api: Instructions file for Claude Code

CLAUDE.md

api CLAUDE.md is an instructions file for Claude Code from iblai/api. It costs 2,797 tokens per session, scanned B, original, MIT.

Repository instructions for an AI agent working on iblai/api, a toolkit that operates the ibl.ai platform through web APIs and a hosted conversation service.

In plain words
What is it for?
Working on ibl.ai API skills, the hosted agent-chat service, repository structure, and naming conventions.
Why use it?
They give the agent the repository’s purpose, terminology, layout, and operation boundaries so it can make consistent changes without relying on the website interface.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is iblai/api's own configuration. It tells Claude Code how to work on api 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 api configures →

Reuse

Borrowing it

Nothing to install: this file belongs to iblai/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.

Copy the file
curl -O https://raw.githubusercontent.com/iblai/api/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/iblai/api

Made for: Claude Code.

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 api CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/iblai/api/claude-md"><img src="https://agentmods.dev/badge/instructions/iblai/api/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,797 This file is loaded in full into every session.
When invoked 2,797 The same file — it is already loaded in full.
Security scan B 2 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.02797 $0.02797
Opus 5.5 $0.01119 $0.01119
Sonnet 5.5 $0.00559 $0.00559
Haiku 4.5 $0.00280 $0.00280

Measured 2mo ago against content hash 0a8f5e680869, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

api CLAUDE.md scanned grade B with 2 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 2mo 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

**Skills vs MCP server — REST vs runtime chat.** Skills do everything reachable over REST (configure agents, datasets, memory, users, roles, notifications, discovery/search, recommendations, user profile + analytics, rep

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

5. `## Example` — one realistic `curl`.
CLAUDE.md · 96 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Repository Purpose

iblai/api is a toolkit for operating the ibl.ai platform from an AI agent. It ships two things:

  1. Skills (skills/) — installable via npx skills add iblai/api. Each /iblai-api-* skill maps one agent-configuration or platform-admin operation to its exact api.iblai.app REST endpoints (method, URL, body). They drive the platform directly — no UI.
  2. MCP server (mcp/) — a single hosted Model Context Protocol server, iblai-api-agent-chat, for the one runtime capability that isn't a REST call: holding a live conversation with a deployed agent (streamed responses, tool use, RAG).

This is the API-driven complement to iblai/vibe, which provides UI components for building ibl.ai apps.

Naming. Skills are iblai-api-*; scope is encoded by prefix. iblai-api-agent-* acts on one agent; iblai-api-profile* on the signed-in user. Org-wide is the default scope, so those skills are bare — iblai-api-management, iblai-api-rbac, iblai-api-crm, iblai-api-token, iblai-api-integration, iblai-api-notification, iblai-api-invite — and iblai-api-org itself is the org-settings skill. Cross-cutting skills are bare too: iblai-api-search, iblai-api-analytics, iblai-api-course-create, iblai-api-login. (These iblai-api-* names overlap some of vibe's; that's accepted.)

Skills describe APIs, not UIs. Each skill documents endpoints (method, URL, body) and when to use them. Do not reference user interfaces (menus, tabs, buttons, pages, "Edit Agent → …") in skill prose — the UI was only a means to discover endpoints; the value is the API.

Skills vs MCP server — REST vs runtime chat. Skills do everything reachable over REST (configure agents, datasets, memory, users, roles, notifications, discovery/search, recommendations, user profile + analytics, reporting). The MCP server is only for live agent chat — and even wiring it up is a skill (/iblai-api-agent-chat writes the .mcp.json / claude mcp add config from the .env token + a chosen agent's unique_id), so the whole offering installs via npx skills add iblai/api. Rule: if a skill covers it, there is no server for it. That's why only iblai-api-agent-chat remains — the former analytics, agent-create, search, and user servers were removed once skills covered analytics (/iblai-api-analytics), agent creation (/iblai-api-agent-create), discovery + recommendations (/iblai-api-search), and user profile + analytics (/iblai-api-profile).

Read the full file on GitHub · 96 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. 2mo ago First seen · 96 lines · 2,797 tokens per session scan B 0a8f5e680869

Subscribe to this mod's changes

api CLAUDE.md is an instructions file published in the GitHub repository iblai/api (15 stars, last pushed 1mo ago), licensed MIT. It adds 2,797 tokens to every session, about $0.0112 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads mcp configuration, makes network calls). 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