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-tool-schemas/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-tool-schemas)<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-tool-schemas"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-tool-schemas.svg" alt="Measured on agentmods" 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.00085 | $0.00599 |
| Opus 5 | $0.00043 | $0.00300 |
| Sonnet 5 | $0.00017 | $0.00120 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
nexus-tool-schemas 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 8d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus Tool Schemas
Context: the exporter boots the agent registry headlessly and asks the live
ToolCliNormalizer for each tool's CLI schema, so the JSON is the caller's-eye
view of the tools rather than a parse of the TypeScript. It runs with no
Obsidian, no vault and no build — but it does need npm install, and it writes
to two different files for two different jobs.
Workflow
- Decide which job this is. The answer is the output path, and choosing it by
default is the standard failure here — the default path is a scratch file
nothing reads.
- Reading, answering a question, inspecting a subset →
protocols/export-subset.md - Refreshing the catalog the repo ships and tests against →
protocols/refresh-catalog.md
- Reading, answering a question, inspecting a subset →
- Run that protocol end to end. You MUST NOT hand-write or hand-patch either JSON file: both are generated, and an edited catalog makes the drift test the only thing standing between a wrong doc and a caller.
- Validate what you produced with
scripts/check_catalog.pybefore reporting it, and treat a non-zero exit as a stop. - At the end of a session that used this skill, run
protocols/self-refine.md.
Map
protocols/the two export jobs, plus self-refine.references/consumers.md(which file each reader expects, and what breaks when it is stale) andexporter-internals.md(how the headless boot works, what it needs, and its failure modes).scripts/check_catalog.pyvalidates an exported catalog;scripts/check_exporter_coverage.pycatches an agent the exporter cannot see. Run them, do not reimplement.refinement-log.mdwhat past sessions changed here and why.
Siblings
- Adding or renaming an agent or tool, or a command that does not resolve:
nexus-agents. It owns the slug-to-CLI-name transform (cli_name.py) and the checker for commands written in docs (check_documented_commands.py). - Jest lanes, the shipped-docs gate and how to make a failing test fail for the
right reason:
nexus-testing. - Shipping the refreshed catalog in a version:
nexus-release.
What ships with it
9 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.
- agents/openai.yaml 254 B
- protocols/export-subset.md 2.8 KB
- protocols/refresh-catalog.md 3.1 KB
- protocols/self-refine.md 1.9 KB
- references/consumers.md 2.9 KB
- references/exporter-internals.md 3.6 KB
- refinement-log.md 1.9 KB
- scripts/check_catalog.py 10 KB runs code
- scripts/check_exporter_coverage.py 3.7 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.
- 8d ago First seen · 46 lines · 85 tokens per session scan A a9b938263ea8
nexus-tool-schemas is a skill published in the GitHub repository ProfSynapse/nexus (154 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 599 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…