oh-my-agent is a harness for checking whether coding agents actually completed their work by verifying tests, required artifacts, independent reviews, and recorded decisions. It is used across multiple agent runtimes to make workflow results auditable instead of relying on an agent's own report. The catalogue add-ons provide parts of its skills, agents, hooks, MCP integrations, instructions, and plugins.
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 first-fluke/oh-my-agent --skill oma-securitygit clone --depth 1 https://github.com/first-fluke/oh-my-agentWrote 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/first-fluke/oh-my-agent/oma-security)<a href="https://agentmods.dev/skills/first-fluke/oh-my-agent/oma-security"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-security/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/first-fluke/oh-my-agent/oma-security"><img src="https://agentmods.dev/badge/skills/first-fluke/oh-my-agent/oma-security.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.00045 | $0.03020 |
| Opus 5.5 | $0.00018 | $0.01208 |
| Sonnet 5.5 | $0.00009 | $0.00604 |
| Haiku 4.5 | $0.00005 | $0.00302 |
Grade A, and why
oma-security 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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanning and Validation
Scheduling
Goal
Run the selected security checks, retain their native evidence, independently validate candidates, and report findings and coverage on the recorded source or deployment identity.
Intent signature
- Requests to scan a repository, agent skill package, MCP component, or web test deployment for vulnerabilities.
- Explicit Deepsec, Cisco Skill Scanner, Cisco MCP Scanner, Cisco AI Deep SAST, ARTEX, or Cloudflare security-audit-skill requests.
- Security scan setup, scoped PR/diff analysis, finding triage/reproduction, scanner failures, or security CI gates.
When to use
- Scan application source or a source diff; inspect skill packages or MCP components.
- Run a bounded runtime penetration test against a concrete authorized test deployment.
- Validate scanner candidates, retain evidence, or configure an engine-specific CI gate.
- Troubleshoot the selected scanner, credentials, coverage, matchers, quota, or resumable state.
When NOT to use
- Broad correctness, performance, accessibility, or quality review ->
oma-qa. - External tool comparisons or research without execution ->
oma-search. - Security architecture decisions ->
oma-architecture. - Product-code remediation ->
oma-debugor the owning backend/frontend/mobile/infrastructure skill. - A security question or a repository's existence alone does not request a scan.
Expected inputs
targetandtarget_type:source | skill | mcp | web_runtime; source/package paths are absolute.intent:setup | scan | diff | pentest | triage | validate | ci | troubleshoot.- Source commit plus dirty-tree digest, package/configuration digest, or deployment/environment/session identity; diff mode also needs a baseline.
- Requested engines, threat model, paths/exclusions, severity/gate policy, existing backend/credential decisions, budget and stop conditions.
- For local reproduction: an OS sandbox, bounded fixtures, resource/time limits, and permitted effects.
- For runtime: exact URL/scheme/host/port, allowlist/exclusions, test-account roles, allowed effects, request/concurrency/time/token/spend limits, and deployed revision/image digest when available.
What ships with it
11 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.
- resources/artex.md 9.1 KB
- resources/ci.md 11 KB
- resources/cisco-source.md 8.3 KB
- resources/deepsec-config.md 3.2 KB
- resources/deepsec-matchers.md 2.6 KB
- resources/deepsec-scanning.md 3.0 KB
- resources/deepsec-setup.md 3.1 KB
- resources/findings-contract.md 28 KB
- resources/mcp-scanning.md 8.0 KB
- resources/skill-scanning.md 7.8 KB
- resources/validation.md 8.0 KB
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 · 173 lines · 45 tokens per session scan A 237d40878e99
oma-security is a skill published in the GitHub repository first-fluke/oh-my-agent (1,352 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 3,020 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-10-11.
Other skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
release-db-config-sync
Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary. green(0) no diff · staged(3) pending migrations/missing keys await approval · blocked(1) real…
release-preflight
Run the release hard-precondition gate before any tag/OTA — apc release preflight runs the real tier gate (run.ts), version alignment, and prisma regen check, all read-only. green(0) releasable · staged(3) fixable preconditions · blocked(1) tier red/envblocked. No push, no write.