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-scimnpx skills add iblai/api --skill iblai-api-scimgit 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-scim)<a href="https://agentmods.dev/skills/iblai/api/iblai-api-scim"><img src="https://agentmods.dev/badge/skills/iblai/api/iblai-api-scim.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.03698 |
| Opus 5 | $0.00000 | $0.01849 |
| Sonnet 5 | $0.00000 | $0.00740 |
| Haiku 4.5 | $0.00000 | $0.00370 |
Grade A, and why
iblai-api-scim 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 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.
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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iblai-api-scim
Provision and manage an organization's directory over the SCIM 2.0 REST API: users (modeled on the SCIM User schema plus the Enterprise User extension) and RBAC groups (exposed via the SCIM Group schema), including RBAC group membership that automatically links users to the platforms behind those groups. Use when standing up or syncing directory provisioning for an org — creating or deactivating users, managing RBAC group membership, or wiring an identity provider's SCIM provisioning.
Scope is exactly two resources:
UsersandGroups. The SCIM app in the DM service registers only these two — there are no Departments, DepartmentMembers, or GroupMembers SCIM endpoints. (Departments and non-RBAC groups still appear inside a user's Enterprise-extension response block, but they are read-only there; there are no SCIM routes to manage them.)
Auth & conventions
- Base URL:
https://api.iblai.app/dm— these are Data Manager (DM) endpoints, so the/dmprefix is required; the/api/orgs/…/scim/v2/…paths below are appended to it (e.g.https://api.iblai.app/dm/api/orgs/{platform_key}/scim/v2/Users). - Header: SCIM accepts two auth schemes (both authentication classes are
wired on every view:
PlatformApiKeyAuthentication,OAuth2ClientCredentialAuthentication):Authorization: Api-Token $IBLAI_API_KEY— the Platform API Token used by the otheriblai-*skills; orAuthorization: Bearer <oauth2-token>— an OAuth2 client-credentials token.
- Content type: send
Content-Type: application/scim+jsonon every write (the server also accepts plainapplication/json). - Path / scope: SCIM paths are
/api/orgs/{platform_key}/scim/v2/...where{platform_key}=$IBLAI_ORG(the org key). The token's scope must match theplatform_keyin the URL. - Resource casing — keep verbatim. Both resources are PascalCase:
UsersandGroups. Do not lowercase them. - Trailing slash — keep verbatim. Collection routes have no trailing
slash (
/Users,/Groups); single-resource detail routes require a trailing slash (/Users/{id}/,/Groups/{id}/). The group action routes (/Groups/{id}/add_members,/Groups/{id}/remove_members) have no trailing slash. - DELETE / destructive calls — confirm with the user first.
- Not connected yet? Run
/iblai-api-loginfirst to populateIBLAI_ORG,IBLAI_USERNAME, andIBLAI_API_KEY.
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 · 264 lines · 0 tokens per session scan A 384ef153d260
iblai-api-scim 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 3,698 tokens. 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…
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.