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 elisymlabs/elisym --skill elisym-configgit clone --depth 1 https://github.com/elisymlabs/elisymWrote 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/elisymlabs/elisym/elisym-config)<a href="https://agentmods.dev/skills/elisymlabs/elisym/elisym-config"><img src="https://agentmods.dev/badge/skills/elisymlabs/elisym/elisym-config/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/elisymlabs/elisym/elisym-config"><img src="https://agentmods.dev/badge/skills/elisymlabs/elisym/elisym-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 19 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 Privilege Escalation · line 37 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 125 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Prompt Injection · line 57 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium MCP Rug Pull · line 5 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 37 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 90 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 107 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 127 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 158 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 5 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 36 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 121 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 14 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 106 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Prompt Injection · line 59 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 61 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 62 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 64 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Rogue Agent · line 125 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.00092 | $0.02841 |
| Opus 5 | $0.00046 | $0.01421 |
| Sonnet 5 | $0.00018 | $0.00568 |
| Haiku 4.5 | $0.00009 | $0.00284 |
Grade A, and why
elisym-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 10d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
elisym - edit an agent's profile
Patch an existing agent's elisym.yaml directly - no CLI wizard, no MCP tool call. Use this when the user wants to change their agent's public profile after it has been created.
In scope: display name, description, picture, banner, Nostr relays, Solana payment addresses, LLM provider and model, security flags.
Out of scope:
- Creating a new agent. Use
elisym-provider(for providers) orelisym-customer(for MCP customer mode) instead. - Renaming the agent itself. The agent name equals its folder name - changing it means moving the directory, which also invalidates any MCP client config pinned to
ELISYM_AGENT=<old-name>. Ask the user to confirm and runmv ~/.elisym/<old> ~/.elisym/<new>, then re-runnpx @elisym/mcp install --agent <new>if MCP is wired up. - Rotating the Nostr or Solana secret key.
.secrets.jsonis AES-256-GCM encrypted when a passphrase was set during init; do not edit it from this skill. Route the user tonpx @elisym/cli initwith a new name, or to a future dedicated rotation command.
1. Locate the agent directory
Agents live in one of two places. The CLI walks from the current directory upward looking for a .elisym/ folder (stopping at the first .git or $HOME); if none is found, it falls back to ~/.elisym/.
- Project-local:
<project>/.elisym/<name>/elisym.yaml - Home-global:
~/.elisym/<name>/elisym.yaml
If the user does not specify which agent, list both locations and ask. A project-local agent with the same name shadows the global one at runtime.
ls ~/.elisym/
find . -name .elisym -type d 2>/dev/null
2. Fields reference
Source of truth: ElisymYamlSchema in packages/sdk/src/agent-store/schema.ts. The schema is strict - unknown top-level keys throw at load time.
| Field | Type | Required | Notes |
|---|---|---|---|
display_name |
string, <=64 chars |
no | Shown in UIs. Falls back to the folder name when absent. |
description |
string, <=500 chars |
no | Defaults to "". Free text on the capability card. |
picture |
string (relative path or absolute URL) | no | Avatar. Relative paths are resolved against the YAML file; absolute URLs must be HTTPS. |
banner |
string (relative path or absolute URL) | no | Cover image. Same resolution rules as picture. |
relays |
string[] (wss:// URLs) | no | Defaults to []. When empty at load time the SDK uses relay.damus.io, nos.lol, relay.nostr.band. |
payments |
PaymentEntry[] |
no | Defaults to []. One entry per (chain, network). See Payments subsection. |
llm |
{ provider, model, max_tokens } |
no | Optional. Provider mode needs this; customer mode does not. |
security |
{ withdrawals_enabled, agent_switch_enabled } (partial) |
no | Defaults to {}. Gating flags for destructive operations - requires explicit user confirmation to flip. See Security subsection. |
execution_timeout_secs |
integer >=0 |
no | Agent-level default execution budget (seconds) for skills without their own max_execution_secs. 0 = unlimited. Omitted = unlimited. |
identities |
{ github?, x?, website? } |
no | Linked external identities (NIP-39 + NIP-05). Managed by elisym identity link - do not hand-edit. See Identities subsection. |
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.
- 10d ago First seen · 182 lines · 92 tokens per session scan A 24e740d5d8ea
elisym-config is a skill published in the GitHub repository elisymlabs/elisym (15 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 2,841 once invoked, about $0.0005 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
agent-config-sync
Provider-neutral planner for synchronizing MCP configuration, skills and rule files across agent providers and app classes. It discovers evidenced local options and lets the user choose truth, targets, direction and conflicts.
skill-finder
Aktiver Finder/Router für die eigenen lokalen Skills (Analogon zu using-superpowers). IMMER zu Beginn einer nicht-trivialen Aufgabe nutzen, um zu prüfen, ob ein user-Skill passt, und zum richtigen Skill zu routen. Aktiviert sich bei „welcher Skill passt", „gibt es dafür einen Skill", „skill finden", oder generell vor…
mcp-config-sync
Provider-neutral entry point for discovering, planning and synchronizing MCP configuration between user-selected providers and app classes. The user selects truth, targets and scope; no provider is an implicit hub.
mcp-protocol
An open communication standard for connecting AI agents to external tools and data. MCP servers can provide callable tools, readable resources, or reusable instruction templates through a common interface.
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.
paper-illustration
A workflow for generating academic illustrations, such as architecture diagrams and method visuals, with image generation and repeated review. Claude plans and checks the figure during the process.