Nerve is a self-hosted runtime for AI agents built around the Claude Agent SDK, providing persistent memory, scheduled execution, task management, skills, and communication channels. It supports personal assistants for individuals and autonomous workers for tasks such as CI monitoring, pull request review, and flaky-test fixes. The catalogue skills extend its agent workflows.
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 ClickHouse/nerve --skill nerve-workspacegit clone --depth 1 https://github.com/ClickHouse/nerveWrote 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/clickhouse/nerve/nerve-workspace)<a href="https://agentmods.dev/skills/clickhouse/nerve/nerve-workspace"><img src="https://agentmods.dev/badge/skills/clickhouse/nerve/nerve-workspace/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/clickhouse/nerve/nerve-workspace"><img src="https://agentmods.dev/badge/skills/clickhouse/nerve/nerve-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 4 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Tool Misuse · line 49 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Agent Snooping · line 138 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00117 | $0.02126 |
| Opus 5.5 | $0.00047 | $0.00850 |
| Sonnet 5.5 | $0.00023 | $0.00425 |
| Haiku 4.5 | $0.00012 | $0.00213 |
Grade A, and why
Nerve Workspace Config 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 14d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Your Own Configuration
Your configuration lives in the workspace. It contains:
config/settings.yaml— shareable settingsconfig/cron/jobs.yaml,config/cron/system.yaml,config/cron/gates/— cronskills/<id>/SKILL.md— skillsSOUL.md,IDENTITY.md,USER.md,AGENTS.md,TOOLS.md— your standing instructions
This is not the Nerve application source code (that's the nerve-dev skill).
First: is this workspace shared?
The answer decides how you change config, so establish it before you start.
The workspace may be a git repository synced from a shared remote (a config repo), in which case config is something a human reviews and merges, and your job is to propose rather than to edit. It may equally be a plain local directory that belongs to this instance alone — that is what an ordinary install looks like.
- Locked instance (lockdown / remote-only) — a PR is the only thing that
works. Direct edits to tracked config are refused (the skill endpoints answer
403, your
Write/Editare declined across that surface), and a change that got in some other way would block every later sync until someone cleared it. - Workspace has a remote, not locked — route every change to the reviewed
surface through
propose_config_change, even though nothing forces you to. A direct write leaves the workspace diverged from the reviewed revision, and sync refuses to merge while anything in that surface —config/,skills/, and the root instruction files — has uncommitted local state (untracked, modified, staged or deleted). So the edit also stops every later config change from reaching this instance until someone commits or drops it.propose_config_changestages in an isolated worktree, so it leaves the live workspace clean — only a direct write dirties it. That covers every route that writes those files, not just an editor:skill_createandskill_update, thePOST/PUT/DELETE /api/skillsendpoints, and a shell command. - No remote, not locked — there is nothing to open a PR against and no
review to route through. Edit the files directly and tell the user what you
changed.
propose_config_changewill refuse, and it is right to.
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.
- 14d ago Changed · +7 lines 762567f20863
- 1mo ago First seen · 169 lines · 117 tokens per session scan A 56499ced8f58
Nerve Workspace Config is a skill published in the GitHub repository ClickHouse/nerve (93 stars, last pushed today), licensed Apache-2.0. It adds 117 tokens to every session and 2,126 once invoked, about $0.0005 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
error-recovery-skill
Handle errors gracefully with retry strategies and fallback patterns.
multi-tool-orchestration-skill
Coordinate multiple tools together for complex multi-step tasks.
tikhub-skill
Scrape TikTok, Douyin, Instagram, YouTube, Twitter/X, Xiaohongshu, Bilibili, Kuaishou, Weibo, Reddit, Threads, LinkedIn and more through the TikHub pay-per-request API - discover endpoints, call them by id, parse any share URL, and check account balance.
stripe-skill
Process payments, manage customers, issue refunds, and handle subscriptions via the Stripe CLI. Pass any Stripe command (customers, charges, paymentintents, refunds, invoices, products, prices, subscriptions) and the tool runs it for you and returns parsed JSON.
whatsapp-db-skill
Query WhatsApp database for contacts, groups, channels, and chat history. Look up contact info, search groups, manage channels, retrieve messages.
agent-builder-skill
How to use the Agent Builder tool (agentbuilder) to inspect your canvas and add tools, skills and teammates while you run, including the rules a hired employee works under.