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 skills/iblai/api/iblai-api-ecosystemnpx skills add iblai/api --skill iblai-api-ecosystemgit clone --depth 1 https://github.com/iblai/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/skills/iblai/api/iblai-api-ecosystem)<a href="https://agentmods.dev/skills/iblai/api/iblai-api-ecosystem"><img src="https://agentmods.dev/badge/skills/iblai/api/iblai-api-ecosystem.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 | $0.00000 | $0.01296 |
| Opus 5 | $0.00000 | $0.00648 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
iblai-api-ecosystem 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 4d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iblai-api-ecosystem
Orientation to the ibl.ai open-source family. Everything ibl.ai ships is built
on one hosted backend — https://api.iblai.app — with each organization (org)
fully isolated (its own users, agents, branding, data). The repos differ only in
what they let you do to that backend: operate it, build on it, fork a finished
product, or host it yourself.
You are already inside iblai/api — the repo whose skills you're reading. This
skill exists so you know where the sibling repos and tooling fit, and which one to
reach for next. It has no endpoints; the detail lives in the reference files below.
The five-repo family
| Repo | What it is | Reach for it when |
|---|---|---|
| iblai/api (this repo) | Management layer — skills that map to exact api.iblai.app REST endpoints, plus one hosted chat MCP server. Operate the platform headlessly from an agent, terminal, or CI — no UI. |
You want to configure agents, datasets, memory, users, roles, notifications, discovery, profiles, or analytics as / commands. Install: npx skills add iblai/api, then run /iblai-api-login. |
| iblai/vibe | Build layer — Next.js SDK, pre-built components, Claude Code skills, and a scaffolding CLI for creating new apps on the backend. Auth is client-side SSO (no API tokens to manage). | You're building a brand-new app on the ibl.ai backend. Install: npx skills add iblai/vibe. See references/app-tooling.md. |
| iblai/os | Sample app — the open-source AI agent platform running at os.ibl.ai. A complete, production-grade codebase (web + native desktop/mobile), built with vibe. | You want a full AI-agent product to fork, point at your org, rebrand, and ship. See references/repos.md. |
| iblai/lms | Sample app — the open-source skills-intelligence platform at lms.ibl.ai: courses, competencies, credentials, analytics. Also built with vibe. | You want a learning/upskilling product to fork and ship. See references/repos.md. |
| iblai/iblai-infra-cli | Deploy layer — provision the backend on your own AWS account or servers with Terraform + Ansible (given access to the backend images). | You need to self-host instead of running against hosted api.iblai.app. See /iblai-api-infrastructure for the details. |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 49 lines · 0 tokens per session scan A 7644fdf440f1
iblai-api-ecosystem is a skill published in the GitHub repository iblai/api (15 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,296 tokens. 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 skills, from other repositories
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.
design-improvement
WHAT - Browser-grounded iterative design improvement. Consumes design-assessment findings, defines direction, prioritizes safe vs ambiguous changes, implements within existing design system, runs app, captures rendered evidence via browser, reviews and iterates. Reuses evidence model — no new scoring framework.
codeql
CodeQL operational workflow — discover/config, run/inspect, triage SARIF findings (rule/query ID, source→sink, evidence), remediate, re-validate. Distinguishes broad MegaLinter linting from semantic security analysis.
design-assessment
WHAT - Evidence-based design-unit assessment orchestrated by project-assessment. Evaluates visual hierarchy, UX friction, interaction, a11y, responsiveness, design-system compliance, and distinctiveness with severity/confidence evidence citations. Reuses project-assessment-evidence semantics — no second framework.