Borrowing it
Nothing to install: this file belongs to ProfSynapse/nexus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ProfSynapse/nexus/main/.claude/skills/nexus-storage/SKILL.mdgit clone --depth 1 https://github.com/ProfSynapse/nexusWrote 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/profsynapse/nexus/nexus-storage)<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-storage"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-storage/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/profsynapse/nexus/nexus-storage"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-storage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.00708 |
| Opus 5.5 | $0.00026 | $0.00283 |
| Sonnet 5.5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
nexus-storage 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 2mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus Storage
Nexus stores data twice on purpose. The sharded JSONL event store is the source of truth; SQLite is a cache that is deleted and replayed on demand. Almost every storage bug in this repo is a write that landed on the wrong side of that line, or a read that ran before the cache was ready.
This router points at the procedure for your job. Working from the router alone is how the three-place schema change becomes a two-place one.
Workflow
-
Pick the job and open its protocol before editing anything:
Your job Protocol Add or change a SQLite table, column or index protocols/change-schema.mdPersist a new kind of data, or make a write survive restart protocols/persist-new-data.mdData is missing, stale, duplicated, slow, or vanished after a rebuild protocols/diagnose-storage.md -
Read
references/storage-model.mdbefore writing any persistence code. It states the three invariants that decide whether a design is legal here. A change that breaks one is a data-loss bug that unit tests will happily pass. -
NEVER hardcode a storage root, and NEVER treat SQLite as authoritative. Resolve roots through the resolvers named in
references/paths-and-layout.md, and write through a repository so the event lands in JSONL first. -
If you touched
SchemaMigrator.tsorschema.ts, runscripts/check_schema_consistency.pyfrom the repo root and treat a non-zero exit as a stop:python3 .claude/skills/nexus-storage/scripts/check_schema_consistency.py . -
Verify at runtime, not just statically. Every protocol here ends in a verification step that a static check cannot substitute for — schema changes fail on the upgrade path and the fresh-install path independently, and cache bugs only appear after a real rebuild.
-
At the end of a session that used this skill, run
protocols/self-refine.md.
Map
protocols/— the procedures: change-schema, persist-new-data, diagnose-storage, self-refine.references/— read on demand:storage-model.md(invariants and rebuild semantics),paths-and-layout.md(roots, resolvers, on-disk shapes, cache backends),schema-rules.md(what a migration may and may not do),failure-modes.md(symptom → cause → fix).scripts/check_schema_consistency.py— proves the three schema definitions agree. Run it; do not eyeball them.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- protocols/change-schema.md 3.6 KB
- protocols/diagnose-storage.md 3.3 KB
- protocols/persist-new-data.md 3.5 KB
- protocols/self-refine.md 2.0 KB
- references/failure-modes.md 22 KB
- references/paths-and-layout.md 3.5 KB
- references/schema-rules.md 3.7 KB
- references/storage-model.md 6.0 KB
- refinement-log.md 15 KB
- scripts/check_schema_consistency.py 13 KB runs code
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.
- 2mo ago First seen · 60 lines · 65 tokens per session scan A 74e1644b6d6a
nexus-storage is a skill published in the GitHub repository ProfSynapse/nexus (158 stars, last pushed 5d ago), licensed MIT. It adds 65 tokens to every session and 708 once invoked, about $0.0003 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
atlas-mssql
SQL Server specifics for Atlas (also Azure SQL and MSSQL): login, dev database and URL scope (mode=schema vs mode=database, the database query parameter), compatibility level and collation, system-generated constraint names, clustered index defaults and datetime2 precision in HCL, GO batches and the delimiter…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.