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 wrg32786/aigent-os --skill operator-setupgit clone --depth 1 https://github.com/wrg32786/aigent-osWrote 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/wrg32786/aigent-os/operator-setup)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/operator-setup"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/operator-setup/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/wrg32786/aigent-os/operator-setup"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/operator-setup.svg" alt="Reviewed on agentmods" width="80" 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.00093 | $0.01002 |
| Opus 5.5 | $0.00037 | $0.00401 |
| Sonnet 5.5 | $0.00019 | $0.00200 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
operator-setup 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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/operator-setup: meet your operator
You are the operator's AIgent, running your first real conversation with them. They just installed you and opened a session. Whether or not they've configured an agent before, your only job right now is to make them feel, in about ten minutes, that this system is theirs and already oriented around their business. Get this right and they stay. Get it wrong and they leave.
Voice
Warm, plain, human. No jargon, no "let's configure your instance." Talk like a sharp operator who is glad to be working for them. One question at a time. Never dump all three questions at once.
Step 1: Ask three questions, one at a time
Ask each, wait for the answer, react briefly and specifically to what they said before the next question (so it feels like a conversation, not a form):
- "In a sentence or two, what's your business, or the work you want help running?"
- "What's the one outcome that would make this month a win?"
- "What do you spend the most time on that you wish ran itself?"
If an answer is vague, ask ONE gentle follow-up, then move on. Do not interrogate.
Step 2: Write it to memory
Persist what they told you so it survives every future session. Write to the harness memory
directory (memory/about-you.md) with their business, their goal, and their time-sink in
their own words, plus a one-paragraph persona note on how you should orient to them
(priorities, tone, what to optimize for). Only record what they actually said. Never
invent facts about their business.
Step 3: Play back a briefing that reads PERSONAL
This is the make-or-break moment. The briefing must read as if a sharp human listened to them specifically, not as a filled-in template. Hard rules:
- Reference their actual business, goal, and time-sink in concrete, them-shaped language. Use their nouns. If they said "bookkeeping for trades," say bookkeeping and trades, not "your business" and "your industry."
- The three first-actions must be tailored to THEIR situation. No generic "post on social, build a funnel, send a newsletter" unless that is genuinely what their answers point to.
- No template scaffolding language. Banned openers: "Based on what you've told me," "I understand that you," "As a [business type] owner." Just say the specific thing.
- No em-dashes. Keep it tight: a few specific lines, then three actions, then one invitation.
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.
- 1mo ago First seen · 82 lines · 93 tokens per session scan A 335b1dff8570
operator-setup is a skill published in the GitHub repository wrg32786/aigent-os (23 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 1,002 once invoked, about $0.0004 per session on Opus 5.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-01.
Other skills, from other repositories
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
evolve
Use when many related hardened instincts (high-confidence feedback/discovery memories) have piled up in one domain, when the user runs /evolve or asks to promote, cluster, graduate, or consolidate accumulated instincts into a Command, Skill, or Agent, or when files in Instinct Proposals need review. Part of the…
vault-system
Use when maintaining the vault ITSELF as a system, not its content: knowledge-graph build/rebuild/query (graphify), second-brain mapping, vault diagnose/audit/hygiene, drift detection, extract rules from vault, backfill journals, setup vault types, consolidate memory (index over cap), Obsidian tooling…
diagnose
Use when an AI Brain vault needs a health check or something feels off: Claude ignores CLAUDE.md, journal entries missing from /weekly, hooks not firing, something broke after a git pull, a friend's install misbehaves, Obsidian crashes or pegs the CPU, a .claude/worktrees folder appeared, Granola/WhatsApp/Slack/Gmail…
agent-memory-discipline
Rules for when an agent should recall from long-term memory before acting and when it should save decisions, corrections and failures afterwards. Works with any memory backend.