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 qaml-ai/camelAI --skill file-sharinggit clone --depth 1 https://github.com/qaml-ai/camelAIWrote 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/qaml-ai/camelai/file-sharing)<a href="https://agentmods.dev/skills/qaml-ai/camelai/file-sharing"><img src="https://agentmods.dev/badge/skills/qaml-ai/camelai/file-sharing.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.00028 | $0.01350 |
| Opus 5 | $0.00014 | $0.00675 |
| Sonnet 5 | $0.00006 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
file-sharing 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 8d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill enables file exchange between you and the user through camelAI's chat interface.
User Uploads
Users can upload files by dragging and dropping onto the chat or clicking the + button. When they upload a file, you'll see a message like:
(user uploaded file to uploads/document-1736712345-abc123.pdf)
Uploads live in workspace-scoped R2. Use the normal file tools with location: "r2" and paths under uploads/.
Reading User Uploads
// List uploaded files
await tools.ls({ location: "r2", path: "uploads" });
// Read a specific text file
await tools.read({ location: "r2", path: "uploads/filename.txt" });
// Read an image; supported images are returned as image tool content
await tools.read({ location: "r2", path: "uploads/image.png" });
If you need a durable copy inside a project, copy it explicitly. For analysis,
prefer reading the mounted upload directly at /uploads/<name> so large inputs
are not duplicated:
await tools.move({
source: { location: "r2", path: "uploads/input.csv" },
destination: { location: "project", project: "analysis-app", path: "input.csv" },
});
Files persist across sessions, so users can reference previously uploaded files.
ZIP Archives
Do not pass an uploaded ZIP to the text read tool or extract it with an
unchecked shell command. Inspect its manifest first, then read any scripts,
Dockerfiles, dependency manifests, or other executable configuration directly
from the archive:
await tools.inspect_archive({ path: "uploads/source.zip" });
await tools.inspect_archive({
path: "uploads/source.zip",
entry: "scripts/setup.sh",
});
After the archive and its executable/configuration entries are understood, use the purpose-built extractor. It rejects traversal paths, links, encrypted or special entries, ZIP bombs, and archives too large to persist safely:
await tools.extract_archive({
path: "uploads/source.zip",
project: "website",
destination: ".",
});
Extraction writes into an existing project so the resulting files are durable and available to the normal project file and deployment tools.
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.
- 8d ago First seen · 162 lines · 28 tokens per session scan A 35a4b46cb717
file-sharing is a skill published in the GitHub repository qaml-ai/camelAI (366 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 1,350 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…