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 skills add iblai/api --skill iblai-api-tokengit 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-token)<a href="https://agentmods.dev/skills/iblai/api/iblai-api-token"><img src="https://agentmods.dev/badge/skills/iblai/api/iblai-api-token/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/skills/iblai/api/iblai-api-token"><img src="https://agentmods.dev/badge/skills/iblai/api/iblai-api-token.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 24 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 28 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 40 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 49 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 48 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00047 | $0.01683 |
| Opus 5.5 | $0.00019 | $0.00673 |
| Sonnet 5.5 | $0.00009 | $0.00337 |
| Haiku 4.5 | $0.00005 | $0.00168 |
Grade A, and why
iblai-api-token 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 1mo 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 -X POST \ How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iblai-api-token
Manage the organization's Platform API Tokens — the keys that authenticate every
ibl.ai API call. List the tokens, create a new Api-Token (the secret is shown only
once), retrieve or update a token by name, and delete a token by name. Tokens are
platform_key-scoped, not agent-scoped.
A token's RBAC authority is controlled by its mode:
owner(default) — the token resolves permissions using its creator's RBAC permissions. Simplest option; the token acts with the owner's authority.token_policies— the token carries its own fine-grained RBAC, independent of the owner. You attach specific RBAC policies/groups to the token, and only those determine what it can do. Use this to issue narrowly-scoped service tokens for a tenant.
Auth & conventions
- Base URL:
https://api.iblai.app - Header:
Authorization: Api-Token $IBLAI_API_KEYon every request. - Path vars:
{org}=$IBLAI_ORG,{username}=$IBLAI_USERNAME. - Host: these endpoints live under
…/dm/api/core/…. - Not connected yet? Run
/iblai-api-loginfirst to populateIBLAI_ORG,IBLAI_USERNAME, andIBLAI_API_KEY.
Reads
- GET
https://api.iblai.app/dm/api/core/platform/api-tokens/?platform_key={org}— list API keys. The list view omitspolicies/groups. - GET
https://api.iblai.app/dm/api/core/platform/api-tokens/{name}?platform_key={org}— retrieve a single token, including its currently associatedpoliciesandgroups. - GET
https://api.iblai.app/dm/api/core/platform/api-tokens/field-permissions/?platform_key={org}— report which RBAC-gated fields (mode,policies_to_add,policies_to_remove,groups_to_add,groups_to_remove) the caller may write. Returns{field: {"write": bool}}. Useful for building the create form. Gated on create access.
Writes
- POST
https://api.iblai.app/dm/api/core/platform/api-tokens/— create a token (returns the secret only once):{ "username": "string (required)", "name": "string (required)", "key": "", "platform_key": "{org} (required)", "created": "ISO datetime (required)", "expires": "'' or seconds-string (required)", "expires_in": "seconds-string | undefined", "mode": "owner | token_policies (optional, default 'owner')", "policies_to_add": "[int] policy IDs (optional, mode=token_policies only)", "groups_to_add": "[int] group IDs (optional, mode=token_policies only)" } - PATCH
https://api.iblai.app/dm/api/core/platform/api-tokens/{name}?platform_key={org}— update a token'smodeand its policy/group associations:{ "mode": "owner | token_policies", "policies_to_add": "[int] policy IDs", "policies_to_remove": "[int] policy IDs", "groups_to_add": "[int] group IDs", "groups_to_remove": "[int] group IDs" } - DELETE
https://api.iblai.app/dm/api/core/platform/api-tokens/{name}?platform_key={org}— delete a key by name. Destructive — confirm with the user first.
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.
- 1mo ago Changed · +78 lines 5fe083e0720a
- 1mo ago First seen · 70 lines · 47 tokens per session scan A a6463fe2f019
iblai-api-token is a skill published in the GitHub repository iblai/api (15 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,683 once invoked, about $0.0002 per session on Opus 5.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
slack-cli
Interact with the official Slack CLI to create, run, deploy, and manage Slack apps, environments, manifests, and triggers. Use when the user asks about Slack app development workflows, not workspace chat automation.
trd
WHAT — Draft and review a Technical Requirements Document (TRD) using the template, typically from an agreed PRD. Covers architecture, data contracts, technical decisions, risks, and test strategy. English for technical artifacts and tickets unless the user asks otherwise.
threnody-fullstack
Build frontend, backend, and API in parallel with Threnody using contract-first DAG waves. Use for full-stack app scaffolding, OpenAPI-first development, parallel UI and service agents, or integration smoke tests after fanout.
contract-testing
Use when authoring OpenAPI/AsyncAPI contracts, generating Microcks samples, setting up Testcontainers mocks, verifying provider contracts, or bridging API contracts across DESIGN → DISTILL → DELIVER phases.
contract-testing-dotnet
Use when the contract-testing-roster resolved a .NET stack for a provider-side contract test. Always provides the baseline WebApplicationFactory + HttpClient integration test recipe; when the Microcks opt-in is enabled, additionally provides the MicrocksContainer + TestEndpointAsync(OPENAPISCHEMA) layer that replays…
contract-testing-python
Use when the contract-testing-roster resolved a Python stack for a provider-side contract test. Always provides the baseline FastAPI TestClient integration test through the app factory; when the Microcks opt-in is enabled, additionally boots the service on a real port with uvicorn and has a MicrocksContainer…