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 ai-ecoverse/slicc --skill upgradegit clone --depth 1 https://github.com/ai-ecoverse/sliccWrote 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/ai-ecoverse/slicc/upgrade)<a href="https://agentmods.dev/skills/ai-ecoverse/slicc/upgrade"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/upgrade/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/ai-ecoverse/slicc/upgrade"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Data Exfiltration · line 54 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- low Supply Chain · line 54 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00132 | $0.02147 |
| Opus 5.5 | $0.00053 | $0.00859 |
| Sonnet 5.5 | $0.00026 | $0.00429 |
| Haiku 4.5 | $0.00013 | $0.00215 |
Grade A, and why
upgrade scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sSL "https://api.github.com/repos/ai-ecoverse/slicc/compare/v${FROM_VERSION}...v${TO_VERSION}" \ How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade
When SLICC boots and discovers that the bundled version (baked into the build at release time from the root package.json) differs from the version it was last seen running, it emits an upgrade lick to the cone. This skill describes how to react.
Event shape
You receive a message like:
[Upgrade Event: 0.4.1→0.5.0]
SLICC was upgraded from `0.4.1` to `0.5.0`.
Released: 2026-04-15T12:00:00Z
Use the **upgrade** skill (...)
The two version strings (from, to) are valid git tags on https://github.com/ai-ecoverse/slicc — the public source repository. The lick message carries a Lick ID: line — you resolve the card with that id.
What to do when you receive an upgrade lick
The runtime renders the upgrade lick as a binary action card automatically — you do not render a sprinkle. The card has exactly two outcomes, which you drive with the lick tools using the Lick ID from the message:
lick_confirm→ Update workspace files. This runsupgrade applywith the stored release versions. Only confirm once the user has decided to pull the new files.lick_dismiss→ clear the card. Use this when the user wants to skip the merge; nothing is changed and the card mutes (✗). The lick will not fire again until the next upgrade.
The card flips to ✓ on confirm / muted ✗ on dismiss. Never auto-run the merge — the user must choose. Reviewing the changelog is not a card action; it is a separate step you can run first to help the user decide.
Before lick_confirm or lick_dismiss, check list_scoops. A scoop that is processing may lose its in-flight work when the runtime moves to the new version. There is no notification — the scoop can look ready / finished, indistinguishable from a clean completion. Wait until every scoop is idle, or expect to re-feed any that were still working. Idle scoops survive.
Which version am I running?
uname -r prints the running version. upgrade status adds the last-booted one, whether a merge is pending, and the exact upgrade apply line to run when it is — that is where --from/--to come from without a card on screen. Realm scripts read globalThis.SLICC_VERSION.
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.
- 1mo ago Changed f9769edf6ffe
- 1mo ago Changed df0c7fbd2f97
- 1mo ago Changed ba4d56fa4e8b
- 1mo ago Changed · +3 lines 0c8d2e61c561
- 1mo ago First seen · 107 lines · 132 tokens per session scan A 82b86c844678
upgrade is a skill published in the GitHub repository ai-ecoverse/slicc (35 stars, last pushed today), licensed Apache-2.0. It adds 132 tokens to every session and 2,147 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
loop-it
Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto…
ship-it
A GitHub delivery workflow that commits completed changes, pushes a branch, creates and merges a pull request, and closes the related issue.
release-aur
Use when creating, updating, reviewing, or publishing Arch User Repository (AUR) packages. Runs /release-aur plan first, reviews PKGBUILD/.SRCINFO/build/namcap evidence, and only recommends /release-aur publish after a GO decision.
versioning-by-impact
Use when completing a task and deciding whether repository changes require a semantic version bump and changelog entry before commit/push.
release
A repository-specific procedure for preparing or publishing a software release, meaning a checked and versioned update made available to users.