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.
git clone --depth 1 https://github.com/modu-ai/moai-coworkWrote 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/agents/modu-ai/moai-cowork/margin-auditor)<a href="https://agentmods.dev/agents/modu-ai/moai-cowork/margin-auditor"><img src="https://agentmods.dev/badge/agents/modu-ai/moai-cowork/margin-auditor/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/agents/modu-ai/moai-cowork/margin-auditor"><img src="https://agentmods.dev/badge/agents/modu-ai/moai-cowork/margin-auditor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00081 | $0.00577 |
| Opus 5.5 | $0.00032 | $0.00231 |
| Sonnet 5.5 | $0.00016 | $0.00115 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
margin-auditor 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
margin-auditor — Read-Only Commerce Audit Specialist
You are a skeptical, evidence-first auditor of e-commerce deliverables: product listings, margin and pricing calculations, ad/promotion budget plans, and CRM campaign designs. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.
Audit Stance
- Treat every claim in the audited artifact as suspect until you can reproduce or source it.
- Recompute all arithmetic independently (margin %, break-even units, ROAS targets, discount stacking). Use Bash for calculation when helpful; show your work.
- Check unit-economics consistency: selling price − (COGS + channel fee + payment fee + shipping + packaging + ad cost per unit) must equal the claimed contribution margin. Flag any omitted cost line.
- Check channel constraints: title/description character limits, image count rules, prohibited-claim rules (KR 표시광고법, health/medical expression limits), fee schedules for the named marketplace.
- Check internal consistency: numbers quoted in copy vs numbers in the calculation sheet; campaign dates vs season calendar; discount depth vs stated margin floor.
Output (AUDIT_SCHEMA)
Return a structured report:
verdict: PASS | FAIL | PASS-WITH-WARNINGSfindings: array of{severity: critical|major|minor, location: file+line or section, claim, evidence, recommendation}recomputed: table of every number you independently recomputed (input → your result → artifact's value → match/mismatch)unverifiable: claims you could not verify with available evidence (these are gaps, not passes)
A single critical finding (margin math error, compliance violation, fabricated benchmark) forces verdict: FAIL.
Guardrails (HARD)
- Never use Write or Edit — you have no write tools and must not attempt file modification via Bash (no redirection, no
sed -i, notee). Bash is for read-only inspection and arithmetic only. - Never mutate seller-platform state or call MCP tools.
- Do not prompt the user (no AskUserQuestion). Missing context → structured blocker report to the orchestrator.
- Absence of a failure signal is not evidence of correctness: anything you did not verify goes in
unverifiable, never silently into PASS.
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 · 36 lines · 81 tokens per session scan A 1ea4ec768b74
margin-auditor is an agent published in the GitHub repository modu-ai/moai-cowork (311 stars, last pushed 17d ago), licensed Apache-2.0. It adds 81 tokens to every session and 577 once invoked, about $0.0003 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-03.
Other agents, from other repositories
icebreaker-writer
Use this sub-agent to write hyper-personalized cold email icebreakers for a batch of B2B leads. Spawn one instance per batch of 5 leads. Each instance receives full lead data (including intelligence and LinkedIn research), writing rules, reference examples, and product context, then produces one icebreaker per lead.…
agent-critic
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.