Borrowing it
Nothing to install: this file belongs to ai-ecoverse/slicc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ai-ecoverse/slicc/main/.agents/skills/slicc-handoff/SKILL.mdgit 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/slicc-handoff)<a href="https://agentmods.dev/skills/ai-ecoverse/slicc/slicc-handoff"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/slicc-handoff/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/slicc-handoff"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/slicc-handoff.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 Agent Snooping · line 31 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 31 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00094 | $0.00878 |
| Opus 5 | $0.00047 | $0.00439 |
| Sonnet 5 | $0.00019 | $0.00176 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
slicc-handoff 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 4d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
slicc-handoff
Use this skill when the user says things like handoff to slicc, move this to slicc, move to the browser, test in the browser, handoff to browser, install this skill in slicc, upskill slicc with this repo, add this skill to slicc, or otherwise asks you to continue the work in the SLICC browser agent or install a skill into it.
What to do
- Compose a single-line, action-oriented instruction.
- Pick a verb prefix:
handoff:<instruction>— continue the task in SLICC.upskill:<github-url>— ask SLICC to install a skill from a GitHub repo.
- Run the script with
--opento open the handoff URL. Show one of:.agents/skills/slicc-handoff/scripts/slicc-handoff --open "handoff:<instruction>".agents/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:<github-url>"
- Tell the user SLICC will show an approval prompt in the Chat tab.
If the user runs a non-default SLICC instance on another port, prefix the call with SLICC_PORT=5720 (or whatever port they chose) so the localhost POST hits the right instance.
How it works
The script builds a URL like https://www.sliccy.ai/handoff?handoff=<urlencoded> (or ?upskill=<urlencoded-github-url>). Two delivery paths fire in parallel:
- Localhost POST to
http://localhost:${SLICC_PORT ?? 5710}/api/handoffwith the structured payload{ verb, target, instruction?, url, title }—verbishandofforupskill,targetis the github URL for upskill or the handoff URL for handoff, andinstructioncarries the prose for handoff. The local server (node-server or the Sliccstart swift-server) rebroadcasts it as anavigatelick to the connected webapp. Profile-independent: reaches SLICC even when the user's default browser is a different Chrome profile than the one SLICC controls. --openopens the URL in the local browser. If that browser profile has the SLICC extension installed,chrome.webRequestparses the response's RFC 8288Linkheader (relhttps://www.sliccy.ai/rel/handofforhttps://www.sliccy.ai/rel/upskill) and emits the navigate lick when one of those rels is present.
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.
- 4d ago First seen · 48 lines · 94 tokens per session scan A b587ec36de43
slicc-handoff is a skill published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed today), licensed Apache-2.0. It adds 94 tokens to every session and 878 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-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.