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 synadia-ai/synadia-agents --skill configuregit clone --depth 1 https://github.com/synadia-ai/synadia-agentsWrote 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/synadia-ai/synadia-agents/configure)<a href="https://agentmods.dev/skills/synadia-ai/synadia-agents/configure"><img src="https://agentmods.dev/badge/skills/synadia-ai/synadia-agents/configure.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 7 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00041 | $0.01491 |
| Opus 5 | $0.00020 | $0.00745 |
| Sonnet 5 | $0.00008 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
configure 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nats-channel:configure - NATS Channel Configuration
Configures the NATS channel plugin: connection context, session name, and
permission handling. State lives in ~/.claude/channels/nats/config.json.
Arguments passed: $ARGUMENTS
Dispatch on arguments
No args - status, list, and offer to change
Read state and give the user a complete picture, then ask:
-
Current config - read
~/.claude/channels/nats/config.json. Show:- Selected context name (or "none - using demo.nats.io")
- Owner override (if set)
- Session name override (if set)
- Connection URL and description from the context file
- Permission mode (
terminalorquery) and whether permission prompts will be relayed as NATS query chunks or handled in the local terminal
-
Available contexts - run the
list-contexts.shscript bundled alongside this skill file to list all NATS CLI contexts with their URL and description. -
Ask the user - show the numbered list of available contexts and ask if they'd like to switch. Example:
- "Currently using
<name>. Available contexts:" - (numbered list)
- "Would you like to switch? Enter a context name or number, or 'no' to keep the current selection." If no config is set, skip straight to asking them to pick one.
- "Currently using
list - list available NATS contexts
Two separate steps - do NOT combine into one Bash call:
- Bash: run the
list-contexts.shscript bundled alongside this skill file. It produces no stdout - it writes to a file. - Read: open
~/.claude/channels/nats/.contextsand present the markdown table to the user.
<context-name> - select a context
- Treat
$ARGUMENTSas the context name (trim whitespace). - Verify
~/.config/nats/context/<name>.jsonexists. If not, show available contexts and error. - Read the context file. Show the URL and description so the user can confirm it's correct.
mkdir -p ~/.claude/channels/nats- Read existing
config.jsonif present; update/add thecontextfield, preserve other fields (likesessionName,permissions). Write back. - Confirm, then show the status view so the user sees where they stand.
What ships with it
1 file 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.
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 · 156 lines · 41 tokens per session scan A eced21f52385
configure is a skill published in the GitHub repository synadia-ai/synadia-agents (77 stars, last pushed 6d ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,491 once invoked, about $0.0002 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
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
developing-genkit-tooling
Best practices for authoring Genkit tooling, including CLI commands and MCP server tools. Covers naming conventions, architectural patterns, and consistency guidelines.