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 EverMind-AI/everos-plugins --skill everos-sdk-upgradegit clone --depth 1 https://github.com/EverMind-AI/everos-pluginsWrote 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/evermind-ai/everos-plugins/everos-sdk-upgrade)<a href="https://agentmods.dev/skills/evermind-ai/everos-plugins/everos-sdk-upgrade"><img src="https://agentmods.dev/badge/skills/evermind-ai/everos-plugins/everos-sdk-upgrade.svg" alt="Measured on agentmods" 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.00066 | $0.01514 |
| Opus 5 | $0.00033 | $0.00757 |
| Sonnet 5 | $0.00013 | $0.00303 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
everos-sdk-upgrade 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 7d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EverOS SDK Migration
Migrate from any SDK version to a target version (default: latest). Currently supports Python only. Go and TypeScript support is planned.
Step 1: Detect language
Search for EverOS SDK references across all supported languages:
Grep pattern="evermemos|everos|everos.cloud|everos_cloud" glob="*.py"
Grep pattern="evermemos|everos|everos.cloud|everos_cloud" glob="*.{go,mod}"
Grep pattern="evermemos|everos|everos.cloud|everos_cloud" glob="*.{ts,json}"
Classify by which files contain SDK references (not just by file existence):
- Python:
evermemos,everos, oreveros_cloudfound in*.py,pyproject.toml,requirements.txt→ ✓ supported - Go:
evermemosoreverosfound ingo.mod,*.go→ ✗ not yet supported - TypeScript:
evermemosoreverosfound inpackage.json,*.ts→ ✗ not yet supported
NOTE: A project may contain go.mod or package.json without using the EverOS SDK in
those languages (e.g., mixed repos, frontend tooling). Only flag a language as detected
when SDK import/dependency references are actually found in that language's files.
If Go or TypeScript SDK usage is detected, warn the user but do not stop:
"Found EverOS SDK references in Go/TypeScript files — migration for these languages is not yet supported. These files will be skipped. Refer to the v1 API documentation for manual migration guidance."
Then proceed with Python migration if Python SDK usage is also detected.
Step 2: Detect current version
Use Grep to search for SDK usage patterns:
Grep pattern="evermemos|everos|everos_cloud" glob="*.{py,toml,txt}"
Determine version from the patterns found:
evermemos+client.v0.= v0everosoreveros_cloud+client.v1.= v1- Higher versions:
client.vN.= vN
Step 3: Determine target version
- If user specified a target (e.g.,
/everos-sdk-upgrade v2), use that. - Otherwise, find the highest version by scanning rule files (Step 4).
What ships with it
3 files 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.
- 7d ago First seen · 142 lines · 66 tokens per session scan A ddc7388a2ba5
everos-sdk-upgrade is a skill published in the GitHub repository EverMind-AI/everos-plugins (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,514 once invoked, about $0.0003 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-31.
Other skills, from other repositories
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
pennylane
Hardware-agnostic quantum ML framework with automatic differentiation. Use when training quantum circuits via gradients, building hybrid quantum-classical models, or needing device portability across IBM/Google/Rigetti/IonQ. Best for variational algorithms (VQE, QAOA), quantum neural networks, and integration with…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
rocm-kernels
Provides guidance for writing and benchmarking optimized Triton kernels for AMD GPUs (MI355X, R9700) on ROCm, targeting HuggingFace diffusers (LTX-Video, SD3, FLUX) and transformers. Core kernels: RMSNorm, RoPE 3D, GEGLU, AdaLN. Includes XCD swizzle, autotune, diffusers integration patterns, and LTX-Video pipeline…
holoscan-install-wheel
Install Holoscan SDK Python wheel via pip into a venv. Use for Python installs; not for native C++/apt or Conda installs.
typing-exclusion-worker
Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured completion summary. Use when running parallel typing-debt workers or when asked to remove modules from pyproject mypy exclusion overrides.