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-profilenpx skills add iblai/api --skill iblai-api-profilegit 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-profile)<a href="https://agentmods.dev/skills/iblai/api/iblai-api-profile"><img src="https://agentmods.dev/badge/skills/iblai/api/iblai-api-profile.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.00057 | $0.01290 |
| Opus 5 | $0.00028 | $0.00645 |
| Sonnet 5 | $0.00011 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
iblai-api-profile 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 PATCH \ How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iblai-api-profile
Manage the signed-in user's own profile via the API: their basic account info,
social links, education, experience, résumé, and memory. The signed-in user
manages their own profile. (To manage an agent's memories from the admin
side, use /iblai-api-agent-memory.)
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. - Hosts: Basic/Social are on the LMS host (
…/lms/api/…); Education, Experience, and Resume are career endpoints on DM (…/dm/api/career/…). - Not connected yet? Run
/iblai-api-loginfirst to populateIBLAI_ORG,IBLAI_USERNAME, andIBLAI_API_KEY.
Reads
Basic & Social
Basic fields (full name, email, title, about, language) and social links are the user's account record.
- GET
https://api.iblai.app/lms/api/user/v1/accounts/{username}— account:name,email,bio(about text),language_proficiencies,social_links, profile image. - GET
https://api.iblai.app/lms/api/ibl/users/manage/metadata/?username={username}— extended profile metadata (e.g. title).
Education
- GET
https://api.iblai.app/dm/api/career/orgs/{org}/education/users/{username}/— list education records.
Experience
- GET
https://api.iblai.app/dm/api/career/orgs/{org}/experience/users/{username}/— list experience records.
Resume
- GET
https://api.iblai.app/dm/api/career/resume/orgs/{org}/users/{username}/— fetch resume + media files.
Memory
Memory covers two personalization flags plus the user's auto-extracted memories:
- Allow AI to learn from conversations and use saved information in responses — personalization flags stored on the user's account (persist via the account/metadata endpoints above).
- The user's own memories (auto-extracted, with the option to add new ones).
These are the same memory objects the admin side manages; see
/iblai-api-agent-memoryfor the memory CRUD endpoints (…/mentors/{mentor}/mentor-memories/), here scoped to the signed-in user.
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 · 111 lines · 57 tokens per session scan A 7595af3c5109
iblai-api-profile is a skill published in the GitHub repository iblai/api (15 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,290 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
handoff
Use when a coding session is getting long, before stopping complex implementation/migration/debugging work, when the operator says "prepare a handoff" / "hand this off" / "continue in a new chat" / "/handoff", or when a long autonomous run needs continuity (Mode run-ledger, announced in chat) — archives the superseded…
teach
Updates the project knowledge base (.vibeflow/) with corrections, new conventions, architectural decisions, or new patterns based on natural language feedback. Also imports patterns from external repos via --from . Edits are placed outside auto-generated markers to survive incremental analyze runs. Use to keep…
vibeflow-teach
Updates .vibeflow/ with corrections, new conventions, architectural decisions, or new patterns from natural language feedback. Also imports from external repos via --from . Use to keep .vibeflow/ accurate as the project evolves.
clean-architecture-testing
Use when it is unclear where a test belongs and what it is allowed to talk to — which test project and layer it goes in, whether it gets a real database, an in-memory fake, or no double at all, and whether a value object or a constructor is worth a test of its own. Also use when layer dependencies must be enforced by…
jira-service-management
Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.
workspace-knowledge-sync
Syncs knowledge to the agentic-harness knowledge base and AGENTS.md learned facts. Use when the assistant discovers new patterns, learns user preferences, workspace facts, or identifies information worth preserving for future sessions. Integrates with platform-engineer (formerly tech-assistant) for automatic trigger…