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-agent-sessionnpx skills add iblai/api --skill iblai-api-agent-sessiongit clone --depth 1 https://github.com/iblai/apiWhat 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.00091 | $0.01887 |
| Opus 5 | $0.00046 | $0.00944 |
| Sonnet 5 | $0.00018 | $0.00377 |
| Haiku 4.5 | $0.00009 | $0.00189 |
Grade A, and why
iblai-api-agent-session 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 3d 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 -N -X POST \ How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iblai-api-agent-session
Drive a deployed agent's chat transport directly and read its sessions.
Where /iblai-api-agent-chat wires a hosted MCP server for conversation, this
skill is the raw REST/SSE (and WebSocket) surface: POST a prompt, stream the
reply, attach metadata that resurfaces as client_context, and list/inspect
the resulting session records. Get IBLAI_ORG/IBLAI_USERNAME/IBLAI_API_KEY
from /iblai-api-login.
Auth & conventions
- Header:
Authorization: Api-Token $IBLAI_API_KEYon every request. - Path vars:
{org}=$IBLAI_ORG,{user}=$IBLAI_USERNAME. - Two hosts — chat is streaming/ASGI:
- Chat turn (SSE / WebSocket) →
https://asgi.data.iblai.app - Session reads/writes →
https://api.iblai.app/dm/api/ai-mentor/orgs/{org}/users/{user}/v1… i.e.…/orgs/{org}/users/{user}/sessions/…
- Chat turn (SSE / WebSocket) →
- Not connected yet? Run
/iblai-api-loginfirst.
Concepts
metadata → client_context passthrough. Every chat turn (WS or SSE) may carry a
metadata object of arbitrary key/values (BaseConsumerPayload.metadata). The runner
folds it into the prompt the agent sees, so the agent can tailor its reply, and the
consumer persists it on the session as Session.metadata["client_context"]. It is
session-level: each turn's metadata overwrites the session's client_context, so
it sticks across turns until you send new keys. Use it to tell one deployed agent
where/why a message arrives (product, plan tier, page, region) without editing its
prompt. It then echoes back on every read below. The sibling field page_content is
also appended to the prompt, but — unlike metadata — is stripped before the message is
saved.
Reads
- GET
…/dm/api/ai-mentor/orgs/{org}/users/{user}/sessions/— list the user's chat sessions. - GET
…/orgs/{org}/users/{user}/sessions/{session_id}/— the session's paginated chat messages (MessageView); the response also carriesclient_context, read from the session'smetadata["client_context"]. - GET
…/orgs/{org}/users/{user}/sessions/{session_id}/tasks/{task_id}/— the chat-history export (DownloadableChatHistory); every item carries aclient_contextfield. Add?to_csv=truefor a CSV whose columns are exactlytype,content,timestamp,client_context. Kicking off (POST) and polling that export task is owned by/iblai-api-agent-history. - Analytics echo: the same value comes back at
summary.client_contextfrom GET…/dm/api/analytics/messages/details/?platform_key={org}&session_id={session_id}— documented under/iblai-api-analytics.
What ships with it
1 file 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.
- 3d ago First seen · 124 lines · 91 tokens per session scan A 8a69a678e5e4
iblai-api-agent-session is a skill published in the GitHub repository iblai/api (15 stars, last pushed 4d ago), licensed MIT. It adds 91 tokens to every session and 1,887 once invoked, about $0.0005 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 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…
implement
Implements a feature from its spec following all guardrails: budget, DoD, anti-scope, and pattern compliance. Runs an 8-phase pipeline (find spec → extract guardrails → load patterns → plan → implement → test → refine → self-verify DoD). Use after gen-spec when you're ready to code. The agent has filesystem access and…
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.