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 Aiqbee/aiqbee-ai --skill braingit clone --depth 1 https://github.com/Aiqbee/aiqbee-aiWrote 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/aiqbee/aiqbee-ai/brain)<a href="https://agentmods.dev/skills/aiqbee/aiqbee-ai/brain"><img src="https://agentmods.dev/badge/skills/aiqbee/aiqbee-ai/brain.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.1 | $0.00028 | $0.01266 |
| Opus 5 | $0.00014 | $0.00633 |
| Sonnet 5 | $0.00006 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
brain scanned grade A with 0 findings 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 7d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aiqbee Brain Management
You are a brain management assistant for the Aiqbee MCP server. Parse the user's arguments and execute the appropriate action.
Command routing
Parse $ARGUMENTS and route to the correct action:
| Command | Action |
|---|---|
(empty) or list |
List all brains |
templates |
List brain templates |
info [name-or-id] |
Get brain details |
create <name> [--template <id>] [--org] [--no-edit] |
Create a brain |
update <name-or-id> [--name <n>] [--desc <d>] |
Update a brain |
delete <name-or-id> |
Delete a brain (ask for confirmation first) |
set <name-or-id> |
Switch MCP config to a brain-specific URL |
unset |
Switch MCP config back to the brain-agnostic URL |
access [name-or-id] |
List users with access |
grant <email> [Read|ReadWrite|Owner] [name-or-id] |
Grant user access |
revoke <email> [name-or-id] |
Revoke user access |
If arguments don't match any command, treat them as a brain name to search for and show its info.
Action details
list (default)
Call aiqbee_list_brains(). Display results as a formatted table with columns: Name, Access Level, MCP Editing, ID. Highlight the brain that matches the current MCP URL if using a brain-specific endpoint.
templates
Call aiqbee_list_brain_templates(). Display as a table with: Name, Description, ID. Mention that users can pass a template ID to create.
info
Call aiqbee_get_brain_info(brain_id). If the argument looks like a name rather than a UUID, first call aiqbee_list_brains() to find the matching brain ID. Show all brain metadata.
create
Call aiqbee_create_brain(name, ...).
--template <id>: Pass asbrain_template_id--org: Setis_personal=false--no-edit: Setallow_mcp_editing=false
After creation, show the new brain's ID and mcpUrl, and ask if the user wants to switch to it (run the set action).
update
Call aiqbee_update_brain(brain_id, ...). If the argument is a name, resolve to ID first via aiqbee_list_brains(). Only pass fields the user explicitly provided.
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.
- 7d ago First seen · 120 lines · 28 tokens per session scan A c9fa8f38ccc7
brain is a skill published in the GitHub repository Aiqbee/aiqbee-ai (7 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 1,266 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
dbrain-processor
Personal assistant for processing daily voice/text entries from Telegram. Classifies content, saves thoughts to Obsidian with wiki-links, generates HTML reports. Integrates Your Business context (clients, projects, CRM). Triggers on /process command or daily 21:00 cron.
autograph
Schema-as-code enforcement for any Obsidian vault. Zero hardcoded domains. Use when creating vault cards, checking vault health, running schema compliance, deduplicating entities, generating MOC indexes, running decay cycles, bootstrapping a vault, fixing wikilinks, finding orphans or backlinks, extracting entities…
braindb-agent
Persistent memory across sessions via the BrainDB agent. Use at conversation start and whenever you need to recall what you know about the user or save new information to long-term memory.