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 handoffgit 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/handoff)<a href="https://agentmods.dev/skills/ai-ecoverse/slicc/handoff"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/handoff.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.01889 |
| Opus 5 | $0.00048 | $0.00945 |
| Sonnet 5 | $0.00019 | $0.00378 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
handoff 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 2d 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 <target> 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.
Handoff
When the user opens a tab whose main-frame response advertises a SLICC handoff via an RFC 8288 Link header, SLICC parses the header and emits a navigate lick event to the cone. This skill tells you how to respond.
Event shape
You receive a message like:
[Navigate Event: https://example.com/somepath]
{
"url": "https://example.com/somepath",
"verb": "handoff" | "upskill",
"target": "<absolute URL — github repo for upskill, page itself for handoff>",
"instruction": "<free-form prose, only present for handoff>",
"branch": "<git branch — upskill only, optional>",
"path": "<sub-path under the repo — upskill only, optional>",
"title": "<page title if available>"
}
branch and path are upskill-only Link params. Their canonical wire form is <https://github.com/owner/repo>; rel="…/upskill"; branch=main; path="skills/foo" — the repo URL is the bare href and the scope is expressed via Link parameters. Either may be absent; when both are present, install only the named sub-path on the named branch.
The verb is the rel that was matched on the response's Link header. SLICC only emits the navigate lick when the rel matched one of the recognised SLICC rels — anything else is ignored.
Recognised verbs
handoff(relhttps://www.sliccy.ai/rel/handoff) — continue a task that another agent started. Thetargetis the page URL itself; theinstructionis the free-form prose to act on.upskill(relhttps://www.sliccy.ai/rel/upskill) — install a skill from a public GitHub repo. Thetargetis the GitHub repo URL.
These are the only two custom rel URIs SLICC matches on the parsed Link header. Anything else is ignored at the parse layer and never reaches you.
What to do when you receive a navigate lick
Each navigate lick carries a Lick ID line plus verb-specific guidance. The two verbs resolve differently — upskill is agent-actionable, handoff stays human-gated.
upskill (agent-actionable)
Install or skip via the lick tools — do NOT render a dip and do NOT run bash: upskill yourself; lick_confirm performs the install.
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.
- 2d ago First seen · 110 lines · 95 tokens per session scan A e96fc82a8061
handoff is a skill published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed today), licensed Apache-2.0. It adds 95 tokens to every session and 1,889 once invoked, about $0.0005 per session on Opus 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
opencli-browser-sitemap
Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…
pinchtab
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, reuse a dedicated automation profile with user approval, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.