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-agent-disclaimergit 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-agent-disclaimer)<a href="https://agentmods.dev/skills/iblai/api/iblai-api-agent-disclaimer"><img src="https://agentmods.dev/badge/skills/iblai/api/iblai-api-agent-disclaimer.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 25 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 63 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 62 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.00055 | $0.00803 |
| Opus 5 | $0.00028 | $0.00402 |
| Sonnet 5 | $0.00011 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
iblai-api-agent-disclaimer 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 -X POST \ How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iblai-api-agent-disclaimer
Manage an agent's disclaimers via the API: the Advisory text (a single field on
the agent's settings/) and the User Agreement (its own create / update /
activate lifecycle). Use when adding legal or advisory notices users must see or
accept.
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,{mentor}= the agent's unique id (e.g.d17dc729-60fd-4363-81a0-f67d9318b03e). - Not connected yet? Run
/iblai-api-loginfirst to populateIBLAI_ORG,IBLAI_USERNAME, andIBLAI_API_KEY.
Reads
- GET
https://api.iblai.app/dm/api/ai-mentor/orgs/{org}/users/{username}/mentors/{mentor}/settings/— Advisory text lives in thedisclaimerfield. - GET
https://api.iblai.app/dm/api/ai-mentor/orgs/{org}/users/{username}/disclaimers/?mentor_id={mentor}&scope=mentor— User Agreement list (readresults[0]for the active agreement).
Writes
- PUT
…/users/{username}/mentors/{mentor}/settings/— save Advisory text:{ "disclaimer": "string" } - POST
…/users/{username}/disclaimers/— create a User Agreement:{ "content": "string (required)", "mentors": ["uuid"], "scope": "mentor", "active": "boolean" } - PATCH
…/users/{username}/disclaimers/{id}/— update content or toggle activation:
or{ "content": "string" }{ "active": "boolean" }
Example
Create and activate a User Agreement for an agent:
curl -X POST \
"https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/disclaimers/" \
-H "Authorization: Api-Token $IBLAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"content": "By continuing, you agree to use this assistant for educational purposes only.",
"mentors": ["'"$MENTOR"'"],
"scope": "mentor",
"active": true
}'
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 · 82 lines · 55 tokens per session scan A 68be3e88dbad
iblai-api-agent-disclaimer is a skill published in the GitHub repository iblai/api (15 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 803 once invoked, about $0.0003 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
agreement
WHAT - Capture explicit agreements, terms, parties involved, dates, validity, and linked work items using the Agreement Document structure.
yuwen-publish-precheck
A Chinese-language review workflow for checking content before publishing it on Douyin, Xiaohongshu, or WeChat Channels.
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…
lov-domain-cutover
A workflow for putting a mainland-China website online after its ICP filing is approved. It verifies the deployment, DNS, HTTPS certificate, domain response, ICP footer, and handling of the old domain.
lov-filing-monitor
A recurring checker for website filing status on official Chinese government or service-provider pages. It compares the latest status with the previous check and keeps a record.