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 automationgit 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/automation)<a href="https://agentmods.dev/skills/ai-ecoverse/slicc/automation"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/automation.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.00077 | $0.01277 |
| Opus 5 | $0.00039 | $0.00639 |
| Sonnet 5 | $0.00015 | $0.00255 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
automation 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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation: webhooks, cron, filesystem watchers
SLICC's automation primitives turn external or VFS-internal events into licks — messages routed to a work unit. Three shell commands set them up:
| Command | Trigger | Use case |
|---|---|---|
webhook |
Inbound HTTP request | Callbacks from external services |
crontask |
Cron schedule | Recurring background work |
fswatch |
VFS create / modify / delete | React to authored content changes |
All three take --scoop <target>, which names a unit, not a species: a scoop name, a cone name, or a folder (cone-<slug>, <name>-scoop). Omit it and events come back to whichever unit you are — the cone you are in, or the scoop itself if you are one. A target naming no live unit is refused at create time (exit 1, listing the valid targets) — create the scoop first, then register the webhook / cron task / watcher against it. A unit that disappears later has its licks dropped, never re-routed.
If you want your own events, omit --scoop — never hardcode cone. All three commands behave identically here, so omitting the flag is always available, and it works the same whether you are a cone or a scoop. The literal folder cone is not a synonym for "me": it belongs to whichever cone currently holds it, and it is handed to the next new cone after the original one is dropped. A skill that hardcodes it delivers its callbacks into another cone's chat in exactly the multi-cone workspaces where the target matters.
A webhook POST also tells you the truth about the delivery. Any 2xx (202 {"ok":true,"accepted":true} from a tray URL, 200 {"ok":true,"received":true} from a local one — check the status class, not one exact shape) means a unit was woken or your --filter dropped the event on purpose; 404 WEBHOOK_NOT_REGISTERED means the id is unknown, and 422 WEBHOOK_TARGET_UNRESOLVED means the target is gone and the event was discarded. A tray URL can also answer 308 TRAY_SUPERSEDED + Location when the tray was reset since you handed the URL out — follow it (any normal HTTP client does, method and body intact) and save the new URL. Tell an external service to treat a non-2xx as a failed delivery and retry: a webhook URL you gave out hours ago is the one shape that outlives the tray it names, and a caller that fires and forgets turns a dead endpoint into a lick that silently never arrives.
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.
- 3d ago First seen · 80 lines · 77 tokens per session scan A 652ceecb53db
automation is a skill published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed today), licensed Apache-2.0. It adds 77 tokens to every session and 1,277 once invoked, about $0.0004 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
agentcore
Run chrome-use on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock…
share
Share a runnable prototype using the user's preferred deployment tool.
devops
Deploy and manage cloud infrastructure on Cloudflare (Workers, R2, D1, KV, Pages, Durable Objects, Browser Rendering), Docker containers, and Google Cloud Platform (Compute Engine, GKE, Cloud Run, App Engine, Cloud Storage). Use when deploying serverless functions to the edge, configuring edge computing solutions…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
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.