New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Moai Ref Secops

by modu-ai in modu-ai/moai-adk

DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning…

Apache-2.0Auto-check passedSecurity

Install Moai Ref Secops

skills CLI
$ npx skills add modu-ai/moai-adk --skill moai-ref-secops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install modu-ai/moai-adk moai-ref-secops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/moai-ref-secops .claude/skills/moai-ref-secops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
moai-ref-secops
GitHub stars
1.2k
Token cost
~2.6k tokens
SKILL.md length
1,046 words
Files
4
Skills in repo
48
Repo updated
First seen
Licence
Apache-2.0

At a glance

DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning…

  • Tasks that involve Web application vulnerabilities
  • SKILL.md covers Three Sub-Domains (modules), Operational Trust Boundaries, Ecosystem-Neutral Tooling and Distinction from…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Prompt injection and agent security

What it does

Moai Ref Secops is an agent skill from modu-ai/moai-adk. DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF rule tuning, and GraphQL/REST depth and rate limiting. Agent-extending skill that amplifies backend, security, and platform-engineering work with production-grade defensive patterns for pipelines…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `modules/api-ops.md`, `modules/container.md` and `modules/devsecops.md`).

It sits in Security, covering Web application vulnerabilities, Prompt injection and agent security and Secrets management. It works with Kubernetes and GraphQL. The repository describes itself as: Agentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Single Go binary, 16… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Web application vulnerabilities
  • Tasks that involve Prompt injection and agent security
  • Tasks that involve Secrets management

Example prompts

  • “/moai-ref-secops”

What it can do on your machine

Read from SKILL.md and the folder at commit 6c55321. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Moai Ref Secops loads about 2.6k tokens when it runs. Until then it costs about 228 tokens; SKILL.md has 1,046 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~228
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from modu-ai/moai-adk at commit 6c55321, republished under its Apache-2.0 licence (© modu-ai). 1,046 words, ~2,648 tokens.

Download SKILL.mdSave it as .claude/skills/moai-ref-secops/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
moai-ref-secops
description
DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF rule tuning, and GraphQL/REST depth and rate limiting. Agent-extending skill that amplifies backend, security, and platform-engineering work with production-grade defensive patterns for pipelines, containers, and running APIs. NOT for: offensive techniques (exploit execution, container-escape attack steps, privilege-escalation procedures, attack tooling), dev-time web-app OWASP Top 10 (see moai-ref-owasp-checklist), LLM/AI security (see moai-ref-llm-security), supply-chain provenance and signing (see moai-ref-supply-chain), or general API design (see moai-ref-api-patterns).
when_to_use
Use when hardening a CI/CD pipeline, scanning infrastructure-as-code for misconfiguration, hardening a container image or Kubernetes cluster, defending…
user-invocable
false
metadata.version
1.0.0
metadata.category
domain
metadata.status
active
metadata.updated
2026-06-24
metadata.tags
devsecops, container, kubernetes, rbac, api-security, owasp-api, cicd, iac-scanning, runtime-detection, waf, reference
progressive_disclosure.enabled
true
progressive_disclosure.level1_tokens
100
progressive_disclosure.level2_tokens
3000

DevSecOps, Container, and API Operational Security Reference

Defensive practitioner reference for the operational layer of a system — the pipeline that builds it, the container and orchestrator that run it, and the API surface it exposes at runtime. Every section is framed as defense, hardening, detection, or verification: it describes the misconfiguration, how to detect it, and how to prevent it, never how to exploit it.

This skill is split into three modules by sub-domain. The overview below gives the shared threat model and an entry point; the depth lives in the modules. The threat model is operational: a pipeline can be subverted to inject a build step, a container can be misconfigured into a host breakout, and a running API can leak one tenant's data to another. The defenses establish least privilege, isolation, detection, and runtime authorization at each layer.

Three Sub-Domains (modules)

Sub-domainModuleCovers
DevSecOpsmodules/devsecops.mdCI/CD pipeline hardening, secret scanning, IaC misconfiguration detection (Terraform / CloudFormation), SAST/DAST integration
Containermodules/container.mdImage scanning, Kubernetes RBAC hardening, container-escape defense (seccomp / AppArmor / read-only root / non-root), runtime threat detection
API operationalmodules/api-ops.mdOWASP API Top 10 operational defense (BOLA / broken-auth detection in production, rate-limit enforcement, server-side authorization), WAF rule tuning, GraphQL/REST depth and complexity limiting

Operational Trust Boundaries

The core defensive insight: each operational layer is a boundary where an attacker who has reached it can move to the next. Defense-in-depth means each boundary assumes the one before it may have failed.

BoundaryOperational riskPrimary defenseModule
Source → pipelineInjected build step, leaked secret, poisoned runnerSigned pipeline, secret scanning, runner isolationDevSecOps
Pipeline → infra configMisconfigured cloud resource (open bucket, permissive IAM)IaC scanning before applyDevSecOps
Image → registryVulnerable base image, embedded secretImage scanning + admission controlContainer
Container → hostContainer escape to the nodeseccomp, AppArmor, read-only root, non-root, drop capabilitiesContainer
Cluster identity → resourcesOver-privileged ServiceAccount, broad RoleBindingLeast-privilege RBAC, PodSecurity admissionContainer
Client → APIBroken object/function authorization, resource exhaustionServer-side authorization, rate limiting, WAFAPI operational

Ecosystem-Neutral Tooling

This skill names tools at the category level. Where a tool is the de-facto cross-ecosystem standard for its category, it is named but framed as "the standard <category> tool" — the concept transfers to any equivalent tool. No single language ecosystem is privileged; pipeline examples are CLI-shape, not language-specific source.

Distinction from moai-ref-owasp-checklist (operational, not dev-time)

The API-operational module covers the runtime/operational half of API security — detecting Broken Object Level Authorization in production traffic, enforcing rate limits at the gateway, tuning a WAF, limiting query depth on a live endpoint. The dev-time half — secure-coding patterns a developer applies while writing the endpoint (parameterized queries, input validation, authentication design, security headers) — lives in moai-ref-owasp-checklist. This skill keeps its coverage operational and does not duplicate them.

Cross-References

  • moai-ref-owasp-checklist — dev-time web-app OWASP Top 10, authentication patterns, input validation, HTTP security headers (the development-time surface; this skill is the operational surface).
  • moai-ref-supply-chain — SBOM, SLSA provenance, Sigstore signing, dependency hygiene (the supply-chain surface that image scanning and pipeline signing here draw on for artifact provenance).
  • moai-ref-llm-security — AI/LLM defensive security (the LLM-specific operational surface, distinct from the general API/container/pipeline surface here).
  • moai-ref-api-patterns — REST/GraphQL API design and error handling (the API-design surface, distinct from the API-operational-defense surface here).

Defensive Severity Levels

LevelLabelActionExample
P0CRITICALBlock releaseContainer runs privileged with host mounts; API endpoint has no server-side object-ownership check
P1HIGHFix before mergePipeline secret exposed in build logs; ServiceAccount bound to cluster-admin
P2MEDIUMFix within iterationNo image scan in the pipeline; no rate limit on an expensive endpoint
P3LOWTrack in backlogWAF in detection-only mode where enforcement is warranted; no GraphQL depth limit on a shallow schema
<!-- moai:evolvable-start id="rationalizations" -->
Show full SKILL.md (443 more words)Show less

Common Rationalizations

RationalizationReality
"The cluster is internal, so RBAC hardening is optional"An internal cluster is reachable from any compromised pod. Least-privilege RBAC is the boundary that stops a single compromised workload from owning the cluster.
"The container runs our own trusted image, so escape defense is overkill"A trusted image with a vulnerable dependency is still an escape risk. seccomp, non-root, and read-only root are cheap and assume the image may be compromised.
"Authorization is handled in the frontend, the API can trust the client"The client is never a trust boundary. Every operational API defense — BOLA in particular — requires server-side object-ownership checks on every request.
"We scan images at build time, runtime detection is redundant"Build-time scanning misses a zero-day disclosed after deploy and misses runtime behavior. Runtime detection catches what static scanning cannot.
"Rate limiting hurts legitimate users, we will add it if abused"Unbounded consumption is an OWASP API Top 10 risk that is exploited before it is noticed. Rate limits and query-complexity caps are the control, not an afterthought.

Assume-breach-by-layer: each operational layer assumes the one before it may have failed — the pipeline assumes a poisoned source, the container a vulnerable image, the API a hostile client. Defense is the control at each layer, not trust in the previous.

<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="red-flags" -->

Red Flags

  • A container runs as privileged, as root, with a writable root filesystem, or with host paths mounted
  • A Kubernetes ServiceAccount is bound to cluster-admin or a wildcard Role
  • An API endpoint returns an object by ID with no server-side ownership check (Broken Object Level Authorization)
  • The CI/CD pipeline echoes secrets into build logs or runs untrusted code on a shared, non-isolated runner
  • Infrastructure-as-code is applied to production without a misconfiguration scan
  • A public-facing API has no rate limit, no query-depth limit, and no request-size cap
  • Runtime detection is absent, so a post-deploy compromise produces no alert
<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="verification" -->

Verification

  • CI/CD pipeline runs secret scanning and IaC misconfiguration scanning before deploy; runners are isolated (see modules/devsecops.md)
  • Container images are scanned and gated by admission control; containers run non-root with a read-only root filesystem, dropped capabilities, and a seccomp profile (see modules/container.md)
  • Kubernetes RBAC follows least privilege; no ServiceAccount is bound to cluster-admin; PodSecurity admission is enforced (see modules/container.md)
  • Runtime-detection rules alert on container-escape and credential-access behavior; alerts route to a responder (see modules/container.md)
  • Every API endpoint enforces server-side object-level and function-level authorization; BOLA is detectable in production traffic (see modules/api-ops.md)
  • Rate limits, request-size caps, and GraphQL/REST depth and complexity limits are enforced at the gateway (see modules/api-ops.md)
  • Operational coverage does not duplicate the dev-time patterns in moai-ref-owasp-checklist; the two are consulted together
<!-- moai:evolvable-end -->

© modu-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in .claude/skills/moai-ref-secops of modu-ai/moai-adk.

  • SKILL.md
  • modules/api-ops.md
  • modules/container.md
  • modules/devsecops.md

Open the folder on GitHubat commit 6c55321

Compare with similar skills

Moai Ref Secops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Moai Ref Secops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Moai Ref Secops this skillmodu-ai/moai-adk1.2k—~2.6kAutomated safety check: PassApache-2.0
Securitytelagod/code-abyss244—~907Automated safety check: PassMIT
Container Securityhardw00t/ai-security-arsenal104—~2.8kAutomated safety check: PassNone
API Security Designvinayaklatthe/microsoft-security-skills175—~2.2kAutomated safety check: PassMIT
Performing Container Security Scanning With Trivymukul975/Anthropic-Cybersecurity-Skills34k—~818Automated safety check: PassApache-2.0
Security Audit 2sundial-org/awesome-openclaw-skills663—~875Automated safety check: PassNone

Similar skills

  • Security

    telagod/code-abyss

    Defensive security engineering judgment, distilled from a stronger model - invoke when THREAT MODELING a system or feature; making security-relevant design decisions (auth, crypto, trust boundaries…

    244 GitHub stars~907 tokensUpdated 2 mo ago
    SecurityAuto-check passed

  • Container Security

    hardw00t/ai-security-arsenal

    Container and Kubernetes security assessment — image vulnerability scanning, SBOM diff analysis, K8s cluster auditing, RBAC privilege mapping, NetworkPolicy review, container escape testing, and…

    104 GitHub stars~2.8k tokensUpdated 5 mo ago
    SecurityAuto-check passed

  • API Security Design

    vinayaklatthe/microsoft-security-skills

    Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Backend & APIsAuto-check passed

  • Performing Container Security Scanning With Trivy

    mukul975/Anthropic-Cybersecurity-Skills

    Runs Trivy across every target type it supports - container images, filesystems, Git repositories, and Kubernetes clusters - for OS and dependency vulnerabilities, IaC misconfiguration, exposed…

    34k GitHub stars~818 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Security Audit 2

    sundial-org/awesome-openclaw-skills

    Fail-closed security auditing for OpenClaw/ClawHub skills & repos: trufflehog secrets scanning, semgrep SAST, prompt-injection/persistence signals, and supply-chain hygiene checks before enabling or…

    663 GitHub stars~875 tokensUpdated 7 mo ago
    SecurityAuto-check passed

  • API Audit

    briiirussell/cybersecurity-skills

    Audit REST, GraphQL, and RPC APIs against the OWASP API Security Top 10 (2023).

    412 GitHub stars~2.8k tokensUpdated 4 mo ago
    Backend & APIsAuto-check: notes

More from modu-ai/moai-adk

All 48 skills in this repo

  • SVG Technical Infographic Author

    modu-ai/moai-adk

    Builds hand-editable SVG diagrams from computed layout coordinates, lints the source and renders a 2x PNG, with rules for when mermaid is the better choice.

    1.2k GitHub stars~5.2k tokensUpdated today
    Auto-check: notes

  • MoAI Foundation Core

    modu-ai/moai-adk

    Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.

    1.2k GitHub stars~5k tokensUpdated today
    Auto-check passed

  • MoAI SPEC Workflow

    modu-ai/moai-adk

    Manages SPEC documents for MoAI-ADK development, with GEARS or EARS requirement notation, acceptance criteria and a link into the Plan-Run-Sync workflow.

    1.2k GitHub stars~5.1k tokensUpdated today
    Auto-check passed

  • MoAI TDD Workflow

    modu-ai/moai-adk

    Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.

    1.2k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • MoAI Worktree Management

    modu-ai/moai-adk

    Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.

    1.2k GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • CI Watch and Auto-Fix Loop

    modu-ai/moai-adk

    Watches a pull request's CI checks after creation, separates required from auxiliary failures, applies limited safe fixes and escalates anything semantic to you.

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Moai Ref Secops

What does Moai Ref Secops do?

DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning…. Moai Ref Secops is an agent skill from modu-ai/moai-adk. DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF rule tuning, and GraphQL/REST depth and rate limiting.

When should I use Moai Ref Secops?

Moai Ref Secops fits situations like: tasks that involve Web application vulnerabilities; tasks that involve Prompt injection and agent security; tasks that involve Secrets management.

How do I install Moai Ref Secops in Claude Code?

Run `npx skills add modu-ai/moai-adk --skill moai-ref-secops -a claude-code`. Or copy the skill folder (.claude/skills/moai-ref-secops in modu-ai/moai-adk) into .claude/skills/moai-ref-secops in your project. Claude Code loads it when a task matches its description.

How do I install Moai Ref Secops in Codex?

Run `npx skills add modu-ai/moai-adk --skill moai-ref-secops -a codex`. Or copy the skill folder (.claude/skills/moai-ref-secops in modu-ai/moai-adk) into .agents/skills/moai-ref-secops in your project. Codex loads it when a task matches its description.

Can I use Moai Ref Secops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add modu-ai/moai-adk --skill moai-ref-secops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moai-ref-secops, .gemini/skills/moai-ref-secops, .github/skills/moai-ref-secops and .opencode/skills/moai-ref-secops in your project.

What does Moai Ref Secops need to run?

SKILL.md names no scripts, command-line tools or credentials: Moai Ref Secops is instructions for the agent only.

Does Moai Ref Secops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Moai Ref Secops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Moai Ref Secops use?

Moai Ref Secops is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Moai Ref Secops use?

About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Moai Ref Secops?

Skills that share tags, products or a category with Moai Ref Secops: Security (telagod/code-abyss, 244 stars), Container Security (hardw00t/ai-security-arsenal, 104 stars), API Security Design (vinayaklatthe/microsoft-security-skills, 175 stars) and Performing Container Security Scanning With Trivy (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Moai Ref Secops?

modu-ai (a GitHub organization) maintains it in modu-ai/moai-adk, which has 1,230 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 7, 2026.

Source: modu-ai/moai-adk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.