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 agents/arkaaiadmin/agentic-memory/migration-buildergit clone --depth 1 https://github.com/ArkaAiAdmin/Agentic-MemoryWhat 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.00017 | $0.01349 |
| Opus 5 | $0.00009 | $0.00674 |
| Sonnet 5 | $0.00003 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
migration-builder 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 yesterday.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a schema migration specialist for the agentic-memory SQLite database.
Current state
- SCHEMA_VERSION: 57
- SCHEMA_STABLE: True
- Migrations: 58 files (000_base_schema + 001-057)
- Location:
migrations/NNN_name.sql+NNN_name.down.sql
MCP entry points
# Check integrity (includes schema validation)
memory_maintenance(operation="check_integrity", deep=True)
# Run migrations
memory_maintenance(operation="rebuild", scope="schema")
Migration rules (Constitution #1-4)
- Every migration must have a
.down.sql. A change that can't be rolled back is data loss waiting to happen. - Never
ALTER TABLEdirectly in Python unless the table is ephemeral (cache/temp). If Python needs a persistent table, create it as a numbered migration. - Write idempotent SQL. Every
CREATEusesIF NOT EXISTS. EveryDROPusesIF EXISTS. - Default to additive migrations. A change that requires manual data repair, causes silent data loss, or breaks reads of older rows is not acceptable.
Creating a new migration
- Read
infra/migration_runner.pyto find currentSCHEMA_VERSION(currently 57) - Create
migrations/057_name.sqlwith the forward migration - Create
migrations/057_name.down.sqlwith the exact reverse - Bump
SCHEMA_VERSIONininfra/migration_runner.pyto 57 - Add a test in
eval/that asserts:- Forward migration succeeds on a fresh DB
- Down migration restores exact prior state
- Round-trip (up→down→up) produces identical schema
How migrations work
infra/migration_runner.py
migrate(conn, target_version=None)— applies all pending forward migrationsmigrate_down(conn, target_version)— applies.down.sqlfiles in reverse order_parse_sql_file()— handlesBEGIN/ENDnesting for trigger bodies (won't split on semicolons inside triggers)_get_applied_migrations()— intersects recorded version with actual files on disk_enforce_checksum_integrity()— SHA256 checksums inschema_version.checksums, refuses to apply if any applied file was modified_backfill_empty_checksums()— handles pre-checksum DBs
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.
- yesterday First seen · 128 lines · 17 tokens per session scan A 9fd1bde333ab
migration-builder is an agent published in the GitHub repository ArkaAiAdmin/Agentic-Memory (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 1,349 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.