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 timurgaleev/memex --skill setupgit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/setup)<a href="https://agentmods.dev/skills/timurgaleev/memex/setup"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/timurgaleev/memex/setup"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
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 →
- high Privilege Escalation · line 154 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 313 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 197 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 243 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 248 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 477 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00025 | $0.05232 |
| Opus 5.5 | $0.00010 | $0.02093 |
| Sonnet 5.5 | $0.00005 | $0.01046 |
| Haiku 4.5 | $0.00003 | $0.00523 |
Grade A, and why
setup 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 1mo 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 — 513 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup memex
Set up memex from scratch. Target: working brain in under 5 minutes on an existing Postgres; under 30 including infrastructure provisioning.
Contract
- Setup completes with a working brain verified by
memex doctor --json(all checks OK). - The brain-first lookup protocol is injected into the project's AGENTS.md or equivalent.
- Live indexing is configured and verified (a test change indexed and found via search).
- Setup choices are tracked on the
tasks/setup-statebrain page so future upgrades know what the user adopted or declined. - No provider API keys are requested; memex uses AWS Bedrock exclusively (Titan for embeddings, Claude Haiku for utility calls, Claude Sonnet for synthesis-tier work), authenticated via IAM.
Install (if not already installed)
Clone the repo on the host, then:
bun install
scripts/init.sh # interactive: secrets prefix, region, connection string
How memex connects
memex connects directly to Postgres over the wire protocol. You need the
database connection string (a postgresql:// URI), not a dashboard URL
or REST key. The password is embedded in the connection string.
The connection string lives in AWS Secrets Manager under
<secrets_prefix>/memex-postgres-url (default prefix: memex). Two gotchas:
- The secret is a parsed URL: a password containing
?#&:=+%must be URL-encoded before upload, or the parse silently mangles it. - Confirm the region: the instance and the RDS endpoint must agree, and Bedrock must be invocable in that region. A mismatched default region is the most common "everything times out" cause.
Do NOT ask for any model-provider API key. memex uses Bedrock via the host's IAM role; there is nothing to paste.
Why managed Postgres
RDS gives you managed Postgres + pgvector (vector search built in):
- No server to manage, automatic backups, snapshots for debugging
- pgvector pre-installed on current engine versions, just works
- Alternative: any Postgres with the pgvector extension (self-hosted, Neon, Railway, etc.) — memex only needs the connection string
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.
- 1mo ago First seen · 513 lines · 25 tokens per session scan A c0624a3c1fc9
setup is a skill published in the GitHub repository timurgaleev/memex (11 stars, last pushed 23d ago), licensed MIT. It adds 25 tokens to every session and 5,232 once invoked, about $0.0001 per session on Opus 5.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
mesh-memory
Self-hosted semantic memory for AI agents via MCP. Save worklogs, decisions, and notes, then recall them across sessions by meaning, not keyword. Postgres + pgvector with auto-tagging.
database-schema-changes
Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
optimize-a-query
Diagnose and fix a slow Postgres query in the builders-stack — read its EXPLAIN plan, find the missing index or the ORM N+1, and confirm the fix. Use when a page or endpoint is slow, a query times out, or pgstatstatements shows a hot query. Pairs with design-a-schema for the index itself.
vector-backend-operations
Select and connect the right vector-store backend for the vector-mcp MCP server — chromadb, postgres/pgvector, qdrant, couchbase, or mongodb — and supply the correct dbtype/connection parameters that every collection and search call needs. Use when the agent must decide which engine to target, wire up…
db-maintenance
A maintenance guide for a SQLite database that stores memories, sessions, and conversation records in one file. SQLite is a database system that can keep data in a single file.