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 ProfSynapse/nexus --skill skillgit 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/skill)<a href="https://agentmods.dev/skills/profsynapse/nexus/skill"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/skill/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/skill"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/skill.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.00112 | $0.01328 |
| Opus 5.5 | $0.00045 | $0.00531 |
| Sonnet 5.5 | $0.00022 | $0.00266 |
| Haiku 4.5 | $0.00011 | $0.00133 |
Grade A, and why
nexus 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus vault CLI
nexus drives a running Nexus (Obsidian) vault from the shell over a local
socket — no MCP config. It has two verbs: discover what you can do, then
execute.
Start here
Run nexus --help first. It is the authoritative, always-current manual —
commands, the context contract, CLI syntax, gotchas, and the tool catalog. It's
offline and instant (no socket), so read it before your first real command
instead of guessing.
For a common task, nexus playbook <name> gives you a ready-to-run recipe
plus your workspaces and the exact tools it needs, in one call. Run
nexus playbook to see what's available (typically: vault-work, organize,
tasks, prompt).
The mindset (this is what --help can't teach you)
- Explore → inspect → exploit. Search/list find locations;
content readgets contents; then you write. A search hit is a{path, score}, not the note — never quote, summarize, or edit from a hit without reading it first. nexus toolsreturns schemas, not data. It's discovery. Don't loop it hoping for vault content — that comes fromnexus use --memory … --goal … -- content read ….--memoryand--goalare real and enforced. You're operating a person's live vault; pass a genuine running summary and objective, not placeholders.--workspaceand--sessionare pass-once. The vault remembers them: name a session and choose its workspace on the first call of a task (or runmemory load-workspace <name>), then omit both — every later call continues that session and inherits its workspace. Nothing defaults silently: a session that never chose a workspace fails with "This session has no workspace yet" (onlymemory list-workspaces/load-workspace/create-workspacerun before the choice). Pass a different value once to switch.nexus contextshows what the vault currently remembers.- You can't escape the vault. Paths are vault-relative;
..,~, and absolute paths are rejected. That's a guardrail, not a bug. - Nothing is destroyed. The AI gets archive (reversible), not delete.
- Windows:
nexus vaultsdiscovers local named pipes. If policy blocks enumeration, pass--vault <name>or setNEXUS_VAULT.
What ships with it
5 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.
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 Changed · +12 lines e069a0f2bd07
- 1mo ago First seen · 91 lines · 112 tokens per session scan A 7c110bc3e222
nexus is a skill published in the GitHub repository ProfSynapse/nexus (157 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 1,328 once invoked, about $0.0004 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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.