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 mountgit 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/mount)<a href="https://agentmods.dev/skills/ai-ecoverse/slicc/mount"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/mount.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.00146 | $0.03260 |
| Opus 5 | $0.00073 | $0.01630 |
| Sonnet 5 | $0.00029 | $0.00652 |
| Haiku 4.5 | $0.00015 | $0.00326 |
Grade A, and why
mount 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 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.
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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mount
The mount shell command bridges remote storage into the VFS. After mounting, read_file, write_file, edit_file, and bash (with cat, ls, etc.) all work against the remote source as if it were a local directory. Four backends:
| Backend | Source URI | Auth |
|---|---|---|
| Local | (no --source) |
OS file picker — cone-only, fails in scoops |
| S3 | s3://<bucket>[/<prefix>] |
Profile-namespaced secrets (s3.<profile>.*) |
| DA | da://<org>/<repo>[/<path>] |
Adobe IMS bearer (reuses the Adobe LLM provider login) |
| AEM | aem://<org>/<site>[/<path>] |
Adobe IMS bearer (same login as DA) |
Choosing a backend from user intent
When the user asks to "mount X", read the request literally before defaulting to local:
| User says | Use this backend |
|---|---|
| "mount my Documents folder" / "mount /tmp" | Local — mount /mnt/documents |
| "mount this S3 bucket: s3://my-bucket/foo" | S3 — mount --source s3://my-bucket/foo /mnt/s3 |
| "mount this R2 bucket" | S3 with a custom-endpoint profile (R2 is S3-compatible) |
| "mount the AEM DA repo for org/site" | DA — mount --source da://<org>/<site> /mnt/da |
| "mount this Adobe DA project" / "mount da.live" | DA |
| "mount this Helix 6 site" / "mount the Source Bus" | AEM — mount --source aem://<org>/<site> /mnt/aem |
| "mount this S3-compatible storage" (MinIO, etc.) | S3 with a custom-endpoint profile |
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 · 181 lines · 146 tokens per session scan A fcbdef42cdc8
mount is a skill published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed today), licensed Apache-2.0. It adds 146 tokens to every session and 3,260 once invoked, about $0.0007 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-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…
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).
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.