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 naveedharri/benai-skills --skill operatorgit clone --depth 1 https://github.com/naveedharri/benai-skillsWrote 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/naveedharri/benai-skills/operator)<a href="https://agentmods.dev/skills/naveedharri/benai-skills/operator"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/operator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/naveedharri/benai-skills/operator"><img src="https://agentmods.dev/badge/skills/naveedharri/benai-skills/operator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 20 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 280 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00156 | $0.05041 |
| Opus 5 | $0.00078 | $0.02521 |
| Sonnet 5 | $0.00031 | $0.01008 |
| Haiku 4.5 | $0.00016 | $0.00504 |
Grade A, and why
operator 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.
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Baalda Operator
Build a personalized Operator prompt that runs the user's Baalda vault on a recurring schedule.
Baalda ground rules (read once, obey throughout)
These are app invariants, not preferences. Breaking them corrupts note identity or the sync state, and the Operator runs unattended, so a broken rule compounds across every run.
- Run from the vault root. The vault root is the folder the user opened in Baalda.
.context/is off-limits. Baalda keeps its SQLite index, CRDT store andconfig.jsonthere. Never read, write, walk or index it. Same for.gitandattachments/.- Write files, don't shell out to move them. Creating and editing
.mdfiles with normal tools is fully supported: the watcher picks the change up in about 150ms and merges it as a CRDT operation, so an Operator edit and a human keystroke coexist instead of clobbering. - Never
mvorrma synced note. A note's identity is adoc_id, not its path. An external move reads as delete plus create: the note gets a newdoc_idand its history, backlinks and share settings do not follow. The Operator moves and renames throughmove_note/move_folderon the Baalda MCP, or not at all. - Prefer
[[wikilinks]]over relative paths so links survive a later move.
Build a personalized Operator prompt that runs the user's second brain on a recurring schedule. The Operator is a fully autonomous maintenance agent — one session = one run, no questions, no confirmations, executes and reports.
This skill does four jobs, in order:
- Discover what the vault already knows. Read
Context/andCLAUDE.mdsilently — extract org name, team scope, brand voice, vault folders, runtime conventions. - Ask only the gaps. Cadence, connectors, DM recipient, budgets, signature. Don't re-ask anything Phase 0 already pulled out of the vault.
- Render and save the personalized prompt locally.
- Schedule it. Hand off to the
scheduleskill (via theSkilltool) so the trigger is wired before the run ends — the user does not need to manually run/schedule create.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 288 lines · 156 tokens per session scan A b193e0f6f7a4
operator is a skill published in the GitHub repository naveedharri/benai-skills (61 stars, last pushed 6d ago), licensed MIT. It adds 156 tokens to every session and 5,041 once invoked, about $0.0008 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
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
career-portfolio
A portfolio-building skill for Korean job seekers that organizes projects and explains their work for development, design, marketing, and planning roles.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
marketing-meta-ads-manager
A skill that manages Facebook and Instagram advertising through Meta’s official connector using natural-language instructions.
collab-conflict
A guide for handling difficult workplace colleagues and recurring communication conflicts.
collab-negotiation
A guide for preparing one-to-one workplace conversations, persuasion, requests, and negotiations.