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 resonatehq/resonate-skills --skill resonate-server-deploymentgit clone --depth 1 https://github.com/resonatehq/resonate-skillsWrote 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/resonatehq/resonate-skills/resonate-server-deployment)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-server-deployment"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-server-deployment/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/resonatehq/resonate-skills/resonate-server-deployment"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-server-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00033 | $0.03262 |
| Opus 5 | $0.00016 | $0.01631 |
| Sonnet 5 | $0.00007 | $0.00652 |
| Haiku 4.5 | $0.00003 | $0.00326 |
Grade B, and why
resonate-server-deployment scanned grade B with 2 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Root/sudo access Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- curl installed How it starts
The opening of the file, as written. The whole thing — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate Server Deployment
Overview
Deploy the Resonate server on Linux systems using systemd for process management. This skill covers installation, configuration of public URLs, JWT authentication setup, and common troubleshooting scenarios.
Deploying on GCP instead? See resonate-server-deployment-cloud-run for the Cloud Run + Cloud SQL variant.
Prerequisites
- Linux system with systemd
- Root/sudo access
- curl installed
- (Optional) openssl for generating JWT keys
- (Optional) jwt-cli for generating tokens
Quick Start
Basic Deployment (No Auth)
# Download and run
curl -L -o deploy-resonate.sh https://example.com/deploy-resonate.sh
chmod +x deploy-resonate.sh
sudo ./deploy-resonate.sh
Deployment with Public URL and JWT Auth
# Generate RSA key pair first
openssl genrsa -out private_key.pem 2048
openssl rsa -in private_key.pem -pubout -out public_key.pem
# Deploy with configuration (setting the public key enables JWT auth)
sudo RESONATE_SERVER__URL=https://resonate.example.com \
RESONATE_AUTH__PUBLICKEY=/path/to/public_key.pem \
./deploy-resonate.sh
Configuration Options
| Environment Variable | Default | Description |
|---|---|---|
RESONATE_VERSION |
v0.9.8 | Server version the install script downloads |
RESONATE_SERVER__PORT |
8001 | HTTP API port |
RESONATE_SERVER__URL |
(none) | Public URL for the server (e.g., https://resonate.example.com) |
RESONATE_AUTH__PUBLICKEY |
(none) | Path to JWT public key file; setting it enables JWT auth (there is no separate enable flag) |
Server Flags Reference
The Resonate server binary accepts these flags:
resonate serve [flags]
Flags:
--server-url string Public URL for the server (included in response headers)
--server-port int HTTP API port (default 8001)
--auth-publickey string Path to JWT public key for authentication
--storage-type string Storage backend: sqlite, postgres, or mysql (default sqlite)
--storage-postgres-url string PostgreSQL connection URL
--storage-mysql-url string MySQL connection URL
--storage-mysql-pool-size int MySQL connection pool size (default 10)
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.
- 12d ago First seen · 498 lines · 33 tokens per session scan B 5c5cbd074cfb
resonate-server-deployment is a skill published in the GitHub repository resonatehq/resonate-skills (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 33 tokens to every session and 3,262 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
golem-profiles-and-environments
Understanding Golem CLI profiles, application environments, and component presets. Use when configuring deployment targets, switching between local and cloud servers, managing CLI profiles, defining environment-specific presets, or understanding how environments, presets, and profiles interact.
golem-deployment-version
Configuring the deployment logical version in the Golem Application Manifest (golem.yaml): the version: source (git tag, git commit hash, static string, or env var), tuning tagPattern/hashFallback/staticFallback/allowDirty, per-environment version overrides, and the versionCheck uniqueness policy. Use when setting up…
golem-cloud-account-setup
Setting up a Golem Cloud account from scratch. Use when creating a Golem Cloud account, authenticating with Golem Cloud via the CLI, setting up a cloud profile, or deploying to Golem Cloud for the first time.
golem-enable-otlp-scala
Enabling the OpenTelemetry (OTLP) plugin for a Scala Golem agent — exporting traces, logs, and metrics to an OTLP collector, adding custom spans with the invocation context API.
golem-deploy
Deploying a Golem application. Use when asked to deploy agents to a Golem server, update running agents, or troubleshoot deployment issues.
golem-rollback
Rolling back a Golem deployment to a previous revision or version. Use when reverting a deployment, restoring a prior environment state, or recovering from a bad deploy.