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/timurgaleev/memex/advisornpx skills add timurgaleev/memex --skill advisorgit clone --depth 1 https://github.com/timurgaleev/memexWhat 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.00070 | $0.01170 |
| Opus 5 | $0.00035 | $0.00585 |
| Sonnet 5 | $0.00014 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
advisor 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 3d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Advisor
Convention: See
conventions/brain-first.md(viaget_skill conventions/brain-first). This skill is the proactive voice of the brain — it tells the owner how to run it better.
Contract
This skill guarantees:
- Read-only. The
advisortool never mutates. It computes a ranked list of actions from existing brain state. - Print, never execute. You SHOW the user the findings and ASK before running any fix. The user owns every decision.
- Bounded nagging. On a cadence, surface only what changed or what's critical; don't repeat an ignored low-severity item every run.
When to run
- On demand when the user asks "how do I get more out of this brain?"
- On a weekly cadence via the scheduled-checkup recipe below (even idle brains get a "here's how to run this better" ping).
How to run it
Call the advisor tool (from the shell: memex call advisor '{}').
The payload is { version, generated_at, worst, findings: [...] }, with
worst as the severity gate: clean, warn, or critical. Each finding has:
severity—critical|warn|infotitle— one-line why-it-mattersfix— the exact action to fix it (amemexshell command or an MCP tool call, stated explicitly)
What to do with the findings
- Read the findings, highest severity first.
- Summarize the top 1-3 to the user in their own channel/voice. Lead with any
criticalitem (e.g. pending migrations). - For each, show the suggested
fixand ask whether to run it. - If they say yes, run exactly the stated fix yourself — a
memexcommand on the host or the named MCP tool call — nothing more. Version-drift findings route toskills/brain-upgrade(the deploy loop), not to an ad-hoc command. - Never run a fix the user didn't approve.
Scheduled checkup recipe (weekly)
Install a weekly checkup via the operator's host scheduler (a systemd timer)
or the agent harness's own scheduler — see skills/cron-scheduler for the
recipe. Keep the prompt THIN — the job just reads this skill and runs the
advisor:
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.
- 3d ago First seen · 116 lines · 70 tokens per session scan A 1be6307c3327
advisor is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed 8d ago), licensed MIT. It adds 70 tokens to every session and 1,170 once invoked, about $0.0003 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
gbrain-briefing
Compile a daily briefing from brain state. Covers active deals, open threads, people in play, and what needs attention.
admin-playbooks
Saved, repeatable admin routines for the sf-intelligence org that batch the right sfi. tools in one request, then synthesize ONE report. Fire when the user asks for a named routine rather than a single fact — "run my pre-deploy checklist", "I inherited this org, give me the tour", "run a security audit", "what's junk…
discord
Discord ops via the message tool (channel=discord).
bear-notes
Create, search, and manage Bear notes via grizzly CLI.
wiki-dashboard
Create dynamic, queryable dashboard views of the Obsidian vault using Obsidian Bases or Dataview. Use this skill when the user says "create a dashboard", "vault dashboard", "show all X as a table", "dynamic view", "query my vault", "build a content index", "show me all concepts/entities/projects", or wants a…
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.