What is nexus-testing?

A testing guide for Nexus, covering tests, the running Obsidian plugin, evaluation checks, and documentation-related failures. Obsidian is the application in which the plugin runs.

Use it to add or change tests, verify behavior in the running plugin, run gated checks, troubleshoot failures, or prepare a change for merging.

A passing test can be misleading when it uses a hand-written mock instead of the real Obsidian application.

How ProfSynapse/nexus configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/ProfSynapse/nexus/main/.claude/skills/nexus-testing/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ProfSynapse/nexus

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-testing/github.svg)](https://agentmods.dev/skills/profsynapse/nexus/nexus-testing)

Your own site

<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-testing"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-testing/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-testing"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,031 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00081	$0.01031
Opus 5.5	$0.00032	$0.00412
Sonnet 5.5	$0.00016	$0.00206
Haiku 4.5	$0.00008	$0.00103

Measured 2mo ago against content hash 5154ca823c2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

nexus-testing 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/check_catalog_target.py, scripts/check_live_lane_gates.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/nexus-testing/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Nexus

Context: every Jest lane resolves obsidian to a hand-written mock — see moduleNameMapper in jest.config.js. A green suite therefore proves the code agrees with tests/mocks/obsidian/, not with Obsidian. Three ranking defects shipped past that suite. Everything below exists to close the gap between what Jest can prove and what the running plugin does.

Workflow

Pick the job and open its protocol. Work from the protocol, not from this router — the router names procedures, it does not contain them.

Job	Protocol
Add or change a test	`protocols/write-a-test.md`
Prove a change works in the running plugin	`protocols/live-loop.md`
No Obsidian here (container / cloud session)	`protocols/headless-obsidian.md`
Run a gated live-smoke lane or the eval harness	`protocols/run-gated-lanes.md`
`shippedGuidanceCommands` or `ToolManagerCliSyntax` is red	`protocols/fix-shipped-docs-drift.md`
Merge a PR (what to run first, how to gate on CI)	`protocols/merge-a-pr.md`
A symptom you cannot place	`references/troubleshooting.md`

Derive every list from the tree, never from a document. This skill states no test counts, no lane inventory and no env-var table on purpose, and you MUST NOT add one — those rot silently and a rotted list is worse than none. references/lanes.md holds the discovery commands.

Before calling a testing change done, run both checks from the repo root and fix anything they print:

python3 .claude/skills/nexus-testing/scripts/check_live_lane_gates.py
python3 .claude/skills/nexus-testing/scripts/check_catalog_target.py

NEVER claim a change is verified in the app on the strength of Jest alone. If the change touches load order, rendering, hydration or anything that only exists once the plugin is running, protocols/live-loop.md is the proof and nothing else is.
At the end of a session that used this skill, run protocols/self-refine.md.

Read the full file on GitHub · 79 lines

Files

What ships with it

13 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.

Changes

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 · 79 lines · 81 tokens per session scan A 5154ca823c2b

Subscribe to this mod's changes

nexus-testing is a skill published in the GitHub repository ProfSynapse/nexus (158 stars, last pushed 5d ago), licensed MIT. It adds 81 tokens to every session and 1,031 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

nexus: Skill for Claude Code