What is nexus-agents?

Instructions for adding, changing, and checking agents and tools in Nexus, a system that exposes internal capabilities through two shared tools. It also describes the requirements those agents and tools must meet.

Use it when creating or modifying a Nexus agent or tool, fixing an unresolved command, changing capability access, or updating the data sent through the tool manager.

It provides the required process for keeping Nexus registrations, permissions, tool data, and documentation consistent.

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-agents/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-agents/github.svg)](https://agentmods.dev/skills/profsynapse/nexus/nexus-agents)

Your own site

<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-agents"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-agents/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-agents"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 798 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.00060	$0.00798
Opus 5.5	$0.00024	$0.00319
Sonnet 5.5	$0.00012	$0.00160
Haiku 4.5	$0.00006	$0.00080

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

Security

Grade A, and why

nexus-agents 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_documented_commands.py, scripts/cli_name.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-agents/SKILL.md · 59 lines

How it starts

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

Nexus agents and tools

Context: Nexus exposes exactly two MCP tools — getTools (discovery) and useTools (execution). Every agent is internal and reached through those two, so adding an agent adds no MCP tool; it adds something discoverable through them. This file routes. The detail loads when you take the path.

Workflow

Get current truth before you write anything. Trust no inventory in any document, including this one — regenerate the catalog and read it. It lists every command a caller can actually type, and it is the artifact the shipped-docs gate reads:

npm run schemas:release                                         # refresh committed catalogs
node scripts/generate-tool-schemas.mjs --output - --selector "storage" # inspect, write nothing
ls src/agents/ src/agents/apps/                                 # who exists
grep -n "slug:" src/agents/<agent>/<agent>.ts                   # that agent's slugs

Take the protocol for the job. Read it before acting; a summarized procedure is one you will improvise.
- Adding a tool to an existing agent: protocols/add-tool.md
- Adding an agent (core or app): protocols/add-agent.md
- Changing the useTools/getTools payload or the CLI grammar: protocols/change-payload-contract.md
- Something already broke: start at references/failure-modes.md, which is keyed by the symptom you are seeing.
You MUST finish at protocols/verify.md, whichever path you took. Discovery and executability fail separately: a tool can register and still not run, and a command that reads correctly in source can advertise under a different name. Neither is visible from a build that passes.
At the end of a session that used this skill, run protocols/self-refine.md.

Map

protocols/ the procedures: add-tool, add-agent, change-payload-contract, verify, self-refine.
references/ read on demand: contract.md (the invariants a change must not break), cli-names.md (what a slug becomes on the command line, and the parsing rules that follow), registration.md (where an agent gets wired and what actually gates one), failure-modes.md (symptom → cause → proof).
scripts/ run them, do not reimplement:
- scripts/cli_name.py — what a slug advertises as, derived from the live transform in source rather than guessed.
- scripts/check_documented_commands.py — every Nexus command written in a doc, checked against the generated catalog. The repo's own shipped-docs test does not read .claude/skills/**, so this is the only thing standing between this skill and a command that no longer resolves.

Read the full file on GitHub · 59 lines

Files

What ships with it

12 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 · 59 lines · 60 tokens per session scan A 98b5ea1f23e9

Subscribe to this mod's changes

nexus-agents is a skill published in the GitHub repository ProfSynapse/nexus (158 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 798 once invoked, about $0.0002 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.

Building agents

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

nexus: Skill for Claude Code