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 agentmods add skills/binary16labs/prime-silo/file_operationsnpx skills add binary16labs/prime-silo --skill file_operationsgit clone --depth 1 https://github.com/binary16labs/prime-siloWrote 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/binary16labs/prime-silo/file_operations)<a href="https://agentmods.dev/skills/binary16labs/prime-silo/file_operations"><img src="https://agentmods.dev/badge/skills/binary16labs/prime-silo/file_operations.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 | $0.00011 | $0.00253 |
| Opus 5 | $0.00005 | $0.00127 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
file_operations 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.
What it actually says
Usage
Use this skill when you need to inspect or modify the codebase, configuration files, or generate output documents. These tools are strictly scoped to the workspace directories (data_in, data_out, etc.).
Tools
write_file(filename, content, workspace="default", subdir="data_out")- Write string content to a file in the workspace. Automatically creates missing directories.read_file(filename, workspace="default", subdir="data_in", encoding=None)- Read the contents of a file. Includes automatic fallback encoding detection.list_files(workspace="default", subdir="data_out")- List all files and their sizes within a workspace subdirectory.
Examples
Action: list_files
Action Input: {"workspace": "c5_test", "subdir": "data_in"}
Observation: Returns a list of files available in the test workspace.
Action: write_file
Action Input: {"filename": "summary_report.md", "content": "# Summary\n...", "subdir": "data_out"}
Observation: Returns a confirmation and a download URL.
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 · 25 lines · 11 tokens per session scan A 26fdc0ccb707
file_operations is a skill published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 11d ago), licensed MIT. It adds 11 tokens to every session and 253 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-31.
Other skills, from other repositories
draw-image
Generate an image from a text prompt using an OpenAI-compatible image generation API (gpt-image-1-mini or compatible). The image is uploaded to the gofile.io public file sharing service and ONLY the public download page URL is returned. Trigger when user asks to draw, paint, generate, or create an image.
compose:subagent
Use when executing implementation plans with independent tasks in the current session.
compose:worktree
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
compose:merge
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
compose:new-skill
Use when creating new skills or editing existing skills for the project or personal skill library.
compose:plan
Use when you have a spec or requirements for a multi-step task, before touching code.