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/siddsachar/row-bot/filesystem_guidenpx skills add siddsachar/row-bot --skill filesystem_guidegit clone --depth 1 https://github.com/siddsachar/row-botWrote 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/siddsachar/row-bot/filesystem_guide)<a href="https://agentmods.dev/skills/siddsachar/row-bot/filesystem_guide"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/filesystem_guide.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.00014 | $0.00378 |
| Opus 5 | $0.00007 | $0.00189 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade B, and why
filesystem_guide scanned grade B with 1 finding 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
* NEVER tell the user to open a terminal or run a command themselves. What it actually says
- FILESYSTEM vs SHELL ROUTING (strict rules):
- The workspace_* file tools (workspace_read_file, workspace_list_directory, workspace_write_file, etc.) ONLY work inside the configured workspace folder. They CANNOT access any other location on the computer. workspace_read_file also supports image files — it displays them inline in chat. To also analyze image contents, use analyze_image with source='file'.
- For ANY path outside the workspace (D:, C:\Users, /home, etc.), ANY terminal command (python --version, git status, pip install, etc.), or ANY system operation: you MUST use run_command. No exceptions.
- NEVER tell the user to open a terminal or run a command themselves. You have run_command — use it directly.
- ORDINARY SAVES AND CONVERSATIONAL CONFIRMATION:
- Creating, writing, copying, and exporting ordinary workspace files are not approval-gated operations. Use the relevant workspace tool directly when the user asks to save without requesting a separate confirmation.
- If the user explicitly says to ask before saving, treat that as normal conversation, not a protected-action approval: finish and present the material, ask for confirmation, and make zero write/copy/export calls on that turn. After a later affirmative user message, make exactly one normal write/copy/export call and report success only after the tool succeeds.
- Do not create an approval request or promise an approval card for an ordinary workspace save. Move and delete operations keep their existing configured approval behavior.
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 · 33 lines · 14 tokens per session scan B 4d9dcce57ed2
filesystem_guide is a skill published in the GitHub repository siddsachar/row-bot (1,480 stars, last pushed 6d ago), licensed Apache-2.0. It adds 14 tokens to every session and 378 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
rich-post
Send a Telegram rich-media post to ANOTHER allowlisted chat via the bot (Bot API 10.1 sendRichMessage) - text, inline images, tables, headings, lists, quotes, collapsible blocks, formulas, collages/slideshows ALL in one message bubble. Use when the owner asks to post somewhere other than the current conversation (the…
telegram-userbot
Подключение и работа с личным Telegram-аккаунтом владельца (userbot, НЕ бот). Используй, когда просят читать личные чаты/переписку/диалоги, искать по своим сообщениям, писать кому-то от своего имени, «зайди в мой телеграм», «подключи мой телеграм», «прочитай личку», «ответь в личке», «перешли сообщение», а также при…
memory-processor
Iva's daily-memory processor. Reads the day's two-sided transcript (daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic…
agent-browser
Браузерная автоматизация для интерактивных веб-задач. Используй, когда нужно открыть сайт, заполнить форму, кликнуть, сделать скриншот, залогиниться, спарсить JS-страницу или протестировать веб-приложение. Триггеры — «зайди на сайт», «заполни форму», «нажми кнопку», «скриншот страницы», «войди в аккаунт», «спарси…
update-recovery
Restore or merge user customizations preserved during an Iva update. Use when the owner says "restore my update changes", "recover my customizations", «верни мои изменения после обновления», «восстанови мои доработки» or asks about an update conflict.
security-defense
Procedures for handling untrusted content, suspected prompt injection, secret exposure, data exfiltration, and manual security inspection. Use for emails, web pages, forwarded messages, webhooks, group content, or a suspected leak. Do not use as a general claim that every command or model call is automatically…