Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/resonatehq/resonate-skillsnpx agentmods add skills/resonatehq/resonate-skills/resonate-server-scylladbWrote 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-scylladb)<a href="https://agentmods.dev/skills/resonatehq/resonate-skills/resonate-server-scylladb"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-server-scylladb/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-scylladb"><img src="https://agentmods.dev/badge/skills/resonatehq/resonate-skills/resonate-server-scylladb.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.00123 | $0.03484 |
| Opus 5.5 | $0.00049 | $0.01394 |
| Sonnet 5.5 | $0.00025 | $0.00697 |
| Haiku 4.5 | $0.00012 | $0.00348 |
Grade B, and why
resonate-server-scylladb 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 2mo 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s localhost:8001 -X POST -H 'content-type: application/json' -d '{ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf localhost:8001/health How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resonate on ScyllaDB
Overview
resonatehq/resonate-on-scylladb is a Go server that implements the Resonate protocol against ScyllaDB. It is an independent implementation of the published protocol — not a storage backend of the core Rust server (resonatehq/resonate).
Two consequences an agent must internalize before writing any config:
- You cannot get ScyllaDB by configuring the core server. There is no
RESONATE_STORAGE__TYPE=scylladb. You run a different binary from a different repository. - It speaks the same HTTP/JSON protocol. Application code, SDK choice, and worker code are unchanged. The only thing that changes is what
RESONATE_URLpoints at.
Related: resonate-server-nats (another provider — NATS-native, not drop-in), resonate-server-postgres (another provider — the protocol inside Postgres, no server process), resonate-server-deployment (core server on systemd), resonate-server-deployment-cloud-run (core server on Cloud Run).
When to use this skill
- The user already operates a ScyllaDB cluster and does not want to add a database for durable execution.
- The user asks whether Resonate can run on ScyllaDB or another wide-column store.
- The user is evaluating durable execution against storage they already run.
When NOT to use this skill
- The user does not already run ScyllaDB. Recommend the core server on Postgres — it is the reference implementation, it is Apache 2.0, and it is what production deployments run today. Do not steer someone onto ScyllaDB for novelty.
- The user needs promise or task search — it is unimplemented here (see Gaps).
- The user is deploying workers, not the server. Worker deployment is unchanged; use the relevant per-SDK skill.
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 · 224 lines · 123 tokens per session scan B 59fe6b5d748e
resonate-server-scylladb is a skill published in the GitHub repository resonatehq/resonate-skills (7 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 123 tokens to every session and 3,484 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, 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
sql-root-cause-analysis
A SQL-based method for finding why a business metric changed, such as revenue, orders, conversion, or cost. SQL is a language for querying data in databases; the method compares periods and breaks changes down by dimensions such as region, product, and channel.
golem-add-ignite-effect
Uses Apache Ignite 2 from an Effect-based Golem agent through @golemcloud/effect-golem/ignite2. Use when connecting to Ignite, running Ignite SQL, or adding transactional database operations to an Effect agent.
golem-add-mysql-effect
Uses MySQL from Effect-based Golem agents through @golemcloud/effect-golem/mysql. Use when connecting to MySQL, running SQL, or adding transactional MySQL operations to an Effect agent.
golem-add-postgres-effect
Using PostgreSQL from an Effect-based Golem agent through @golemcloud/effect-golem/postgres. Use when connecting to PostgreSQL, running SQL, or adding PostgreSQL transactions to an Effect Golem application.
golem-add-mysql-go
Using MySQL from a Go Golem agent via the golem/rdbms/mysql wrapper. Use when the user asks to connect to MySQL, run SQL, scan rows, or execute a MySQL transaction in a Go Golem project.
golem-add-postgres-go
Using PostgreSQL from a Go Golem agent via the golem/rdbms/postgres wrapper. Use when the user asks to connect to PostgreSQL, run SQL, scan rows, or execute a Postgres transaction in a Go Golem project.