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 agentmods add skills/arbazkhan971/godmode/devsecopsnpx skills add arbazkhan971/godmode --skill devsecopsgit clone --depth 1 https://github.com/arbazkhan971/godmodeWhat 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 | $0.00047 | $0.02568 |
| Opus 5 | $0.00023 | $0.01284 |
| Sonnet 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 2d 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.
- 2d ago First seen · 297 lines · 47 tokens per session scan A 39103b62b6a3
devsecops is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 2,568 once invoked, about $0.0002 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-30.
Other skills, from other repositories
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
influence-psychology
Apply the seven principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity, unity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users dont convert", "ethical persuasion", "reciprocity", "scarcity tactics", "commitment…
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with…
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.