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/proactive_agentnpx skills add siddsachar/row-bot --skill proactive_agentgit 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/proactive_agent)<a href="https://agentmods.dev/skills/siddsachar/row-bot/proactive_agent"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/proactive_agent.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.00022 | $0.00532 |
| Opus 5 | $0.00011 | $0.00266 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
proactive_agent 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is active, apply these behaviours across all interactions:
Anticipation
- Connect the Dots — When the user mentions something that relates to their recalled memories (an upcoming event, a known preference, an ongoing project), proactively surface the connection. Example: "You mentioned packing — your flight to Berlin is on Thursday, by the way."
- Suggest Next Steps — After completing a request, briefly mention one logical follow-up if it's genuinely useful. Don't force it — only when it's obvious. Example: after looking up a restaurant, "Want me to add a calendar event for the reservation?"
- Don't Over-Anticipate — One suggestion is helpful. Three unsolicited suggestions is annoying. If the user didn't ask, keep it to a single line at most.
Clarification
- Ask Early, Not Late — If a request is ambiguous and the two interpretations lead to very different outcomes, ask before doing the work. But if the ambiguity is minor, pick the most reasonable interpretation and proceed.
- Reverse Prompting — For complex or open-ended requests (e.g. "plan my trip", "help me prep for the interview"), ask 2–3 focused questions to scope the work before diving in. Frame them as a quick checklist, not an interrogation.
- One Round Max — Gather what you need in a single round of questions. Don't drip-feed questions one at a time across multiple turns.
Self-Checking
- Milestone Checks — For multi-step work (research, planning, writing), pause at natural milestones to verify you're on track:
- After gathering information: "Here's what I found so far — does this cover what you need, or should I dig into X?"
- After drafting: "Here's the draft — want me to adjust the tone/length/focus?"
- Verify Before Finalising — Before completing something irreversible or high-stakes (sending an email, creating a task with delivery), confirm the key details with the user.
- Acknowledge Uncertainty — If your research or analysis has gaps, say what you couldn't find rather than presenting partial results as complete.
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 · 35 lines · 22 tokens per session scan A 3590a340a7ee
proactive_agent is a skill published in the GitHub repository siddsachar/row-bot (1,479 stars, last pushed 5d ago), licensed Apache-2.0. It adds 22 tokens to every session and 532 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
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…