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 arbazkhan971/godmode --skill devsecopsgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/devsecops)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/devsecops"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/devsecops/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/arbazkhan971/godmode/devsecops"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/devsecops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 249 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 252 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00047 | $0.02568 |
| Opus 5.5 | $0.00019 | $0.01027 |
| Sonnet 5.5 | $0.00009 | $0.00514 |
| Haiku 4.5 | $0.00005 | $0.00257 |
Grade A, and why
devsecops 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevSecOps — Secure Pipeline Integration
Activate When
- User invokes
/godmode:devsecops - User says "secure pipeline", "add SAST", "security scanning", "shift left"
- User says "container scan", "dependency scan", "secret scanning in CI"
- User says "security gate", "block deploys on vulnerabilities"
- Building CI/CD pipelines that handle sensitive code or data
- After
/godmode:pentestreveals issues to catch automatically - When
/godmode:cicdneeds security controls integrated - Compliance requires automated security testing (SOC2, PCI-DSS, HIPAA)
Workflow
Step 1: Pipeline Security Assessment
Evaluate the current CI/CD pipeline security posture:
PIPELINE SECURITY ASSESSMENT:
CI/CD Platform: <GitHub Actions | GitLab CI | Jenkins |
CircleCI | Azure DevOps | Bitbucket>
Source control: <GitHub | GitLab | Bitbucket | Azure Repos>
Artifact registry: <Docker Hub | ECR | GCR | ACR | GHCR>
Deployment target: <K8s | ECS | Lambda | VMs | PaaS>
CURRENT SECURITY CONTROLS:
┌────────────────────┬──────────┬───────────────────────┐
| | Control | Status | Tool | |
├────────────────────┼──────────┼───────────────────────┤
| | SAST | YES/NO | <tool or none> | |
| | DAST | YES/NO | <tool or none> | |
...
Step 2: SAST Integration (Static Application Security Testing)
Configure static code analysis for security vulnerabilities.
All security workflows share a common trigger (adjust per org policy):
# Common trigger pattern for all security scanning workflows
on:
pull_request:
branches: [main]
push:
branches: [main]
Semgrep
#.github/workflows/sast-semgrep.yml
name: SAST — Semgrep
# trigger: on pull_request + push to main (see common trigger pattern)
SEMGREP CONFIGURATION:
Rulesets:
- auto (Semgrep-curated rules for detected languages)
- p/owasp-top-ten (OWASP Top 10 coverage)
- p/cwe-top-25 (CWE Top 25 most dangerous weaknesses)
- p/security-audit (broad security patterns)
- p/<language>-security (language-specific rules)
Custom rules directory:.semgrep/
Create custom rules for project-specific patterns:
- Banned functions (eval, exec, unsafe APIs)
- Required patterns (input validation on routes)
...
CodeQL
#.github/workflows/sast-codeql.yml
name: SAST — CodeQL
# trigger: same as Semgrep (PR + push to main)
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 · 297 lines · 47 tokens per session scan A 39103b62b6a3
devsecops is a skill published in the GitHub repository arbazkhan971/godmode (27 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 2,568 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-08-30.
Other skills, from other repositories
senior-devops
DevOps for CI/CD, containers, Kubernetes, and Terraform. Use when building pipelines, containerizing apps, managing clusters, provisioning cloud infra, deploying with blue- green/canary, or handling infrastructure incidents.
deployment-cicd
Deploy applications with confidence using CI/CD pipelines, containerization, and infrastructure as code. Covers GitHub Actions, Docker, Vercel, and cloud deployment patterns. Triggers on deployment, CI/CD, Docker, GitHub Actions, or DevOps requests.
docker-build-deploy
Use when containerizing a Node.js app and setting up GitHub Actions CI/CD to build, push to GHCR, and deploy via SSH. Multi-stage build, non-root user, caching.
docker-devops
Create optimized Docker configurations, docker-compose setups, Kubernetes manifests, and CI/CD pipelines. Use when containerizing applications, setting up deployment infrastructure, or automating builds. Triggers on: Docker, Dockerfile, container, docker-compose, Kubernetes, k8s, CI/CD, GitHub Actions, deployment.
DevOps Pipeline Builder
Design and implement CI/CD pipelines, Docker configurations, deployment strategies, and infrastructure automation with production-ready patterns.
deploy-planner
Deployment and DevOps agent that generates Dockerfiles, CI/CD configs, and step-by-step deployment guides for free hosting platforms. Triggers on: deploy, launch, hosting, Docker, CI/CD, production, go live, ship it.