OpenMausBot is an open-source chat application where users interact with multiple AI bots, each backed by an agent, model, computer, and connected apps. It is for people who want to run Claude, Codex, or Grok-based agents locally through a messaging-style interface. Its catalogue add-ons provide skills and instructions for working with the application.
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 milind-soni/OpenMausBot --skill create-verification-skillgit clone --depth 1 https://github.com/milind-soni/OpenMausBotWrote 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/milind-soni/openmausbot/create-verification-skill)<a href="https://agentmods.dev/skills/milind-soni/openmausbot/create-verification-skill"><img src="https://agentmods.dev/badge/skills/milind-soni/openmausbot/create-verification-skill/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/milind-soni/openmausbot/create-verification-skill"><img src="https://agentmods.dev/badge/skills/milind-soni/openmausbot/create-verification-skill.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.00039 | $0.00658 |
| Opus 5.5 | $0.00016 | $0.00263 |
| Sonnet 5.5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
create-verification-skill 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 13d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a verification skill
Create one compact, project-specific SKILL.md through skill_manage, which
shows the person every change with an Undo. Do not install skill files
directly or silently add scripts to the user's project.
1. Inspect before drafting
Use the tools already mounted on this bot to establish:
- the exact project or app being verified;
- its existing launch command and reliable ready signal;
- the safest available control surface: existing project CLI, browser, computer, phone, or shell;
- one read-only health check;
- up to three important user workflows and the observable result that proves each one worked;
- how to stop only the process or resource started by the verification run.
Prefer an existing control surface. If the project has no dependable way to launch or drive the relevant workflow, report that prerequisite instead of inventing commands, selectors, APIs, or a new control program.
2. Prove one workflow
Run the real launch, health check, one representative workflow, evidence capture, and cleanup once. Use an isolated test profile or temporary data when available; never drive the user's live data merely to author the skill. If the workflow cannot be proved with the tools currently mounted, stop and explain which capability is missing.
3. Draft one self-contained skill
The proposed SKILL.md must contain YAML frontmatter and these sections:
- Launch — exact command, isolated data/profile, ready signal.
- Doctor — one read-only check with an actionable failure message.
- Drive — stable names, accessibility targets, routes, refs, or commands; never recorded screen coordinates.
- Evidence — action plus resulting state and any important side effect.
- Cleanup — stop only what this run started; preserve the evidence.
- Feature map — at most three proven workflows, each with the user path, control recipe, success proof, and known gotcha.
- Maintenance — re-run Doctor and the affected workflow when the app changes; update drifted instructions but never hide a product failure.
What ships with it
1 file 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.
- 13d ago Changed · +1 lines · -1 tokens per session 6ce1a82fdf77
- 1mo ago Changed · -1 lines 61465aa70651
- 1mo ago First seen · 66 lines · 40 tokens per session scan A 613d582b3a2a
create-verification-skill is a skill published in the GitHub repository milind-soni/OpenMausBot (5,299 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 658 once invoked, about $0.0002 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-02.
Other skills, from other repositories
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
fix-ci
Fix the failed CI checks for the current session. Use when the user requests a CI fix via the Fix Checks button in the Changes toolbar.
winui-ui-testing
Write and run automated UI tests for Windows desktop apps (WinUI 3, WPF, WinForms, Win32) with the winapp ui harness: one batch script, assertions, input, file pickers, dialogs, screenshots, locally or in Windows Sandbox. Use when asked for UI tests or to verify a feature end to end.
winapp-sandbox
Run, debug, and UI-automate a Windows app in a persistent Windows Sandbox rather than the user's desktop. Use for disposable app testing, guest diagnostics, file transfer, and app or whole-desktop evidence. Builds remain on the host; connection and reconnect can briefly take focus.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.