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 mrzhangguoguo/oh-my-workbuddy --skill security-reviewgit clone --depth 1 https://github.com/mrzhangguoguo/oh-my-workbuddyWrote 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/mrzhangguoguo/oh-my-workbuddy/security-review)<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/security-review"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/security-review/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/mrzhangguoguo/oh-my-workbuddy/security-review"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/security-review.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.00021 | $0.00208 |
| Opus 5 | $0.00010 | $0.00104 |
| Sonnet 5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
security-review 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 11d 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.
What it actually says
Ported from oh-my-codex
security-review. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Security Review — deprecated
Hard-deprecated. Do not invoke or route this skill.
When security concerns are in scope, invoke the code-review skill (skill: code-review) and ask it to emphasize security/OWASP checks (injection, authn/authz, secrets, input validation, dependency CVEs). The code-review skill runs inside WorkBuddy with no omx binary and no .omx/ directory.
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.
- 11d ago First seen · 17 lines · 21 tokens per session scan A 4929a96b4544
security-review is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 208 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-31.
Other skills, from other repositories
Security Audit Checklist
A PASS/FAIL/N/A checklist covering injection, authorization, secrets handling, dependency risk, and input validation for reviewing a diff or codebase.
PR Standards
Pull request description, review depth, and merge standards so every PR carries enough context to review and merge safely.
Agent Instruction Drift Check
Procedure for comparing an agent-facing instruction doc (AGENTS.md/CLAUDE.md-style) against the actual current code and configuration to find and flag mismatches.
Security Checklist
A structured PASS / FAIL / N/A checklist covering common risk categories for reviewing a diff before merge.
code-review
Structured code review focusing on correctness, security, and maintainability. Correctness before style. Every reviewer comment must be actionable.
code-review-self
A self-review checklist for checking code before committing it or opening a pull request, which is a request for teammates to review proposed changes.