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 dungnotnull/hybrid-harness-chaos-process-prm --skill s11-security-scanninggit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s11-security-scanning)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s11-security-scanning"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s11-security-scanning/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/dungnotnull/hybrid-harness-chaos-process-prm/s11-security-scanning"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s11-security-scanning.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.00124 | $0.03730 |
| Opus 5 | $0.00062 | $0.01865 |
| Sonnet 5 | $0.00025 | $0.00746 |
| Haiku 4.5 | $0.00012 | $0.00373 |
Grade A, and why
security-scanning 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 12d 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 — 510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanning & Vulnerability Management (s11)
Purpose
Establish a zero-tolerance security gate across the entire delivery pipeline — catching vulnerabilities at every layer (code, dependencies, containers, infrastructure, secrets) before they reach production. Generate SBOMs for every artifact and maintain an auditable security posture visible to compliance teams.
Prerequisites
- Source code repository available for scanning
- Container images built and pushed to a registry
- Harness STO addon enabled in the pipeline
- Security scanning tools configured (Semgrep, Trivy, Snyk/OWASP DC)
- Gitleaks installed for secrets detection
- Access to vulnerability database (internet or mirrored)
Input Contract
| Input | Source | Required |
|---|---|---|
| Source code repository | s05 (service definitions) | Yes |
| Container image references | s04 (pipeline artifacts) | Yes |
| Dependency manifests (package.json, go.mod, requirements.txt) | Source code | Yes |
| Infrastructure-as-code (Terraform, CloudFormation, K8s manifests) | s10 (GitOps repo) | Yes |
| Security policy requirements | s01 (PRD compliance section) | No |
| Previous vulnerability scan results | Previous s11 runs | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| SAST scan report (Semgrep) | .commandcode/artifacts/security/sast-report.json |
JSON |
| Container scan report (Trivy) | .commandcode/artifacts/security/container-scan.json |
JSON |
| Dependency scan report (Snyk/OWASP) | .commandcode/artifacts/security/dependency-scan.json |
JSON |
| Secret detection report (Gitleaks) | .commandcode/artifacts/security/secret-scan.json |
JSON |
| IaC security scan (Checkov/tfsec) | .commandcode/artifacts/security/iac-scan.json |
JSON |
| SBOM (CycloneDX/SPDX) | .commandcode/artifacts/security/sbom.json |
JSON |
| Security gate verdict | s04 (pipeline gate), s22 (policy input) | Boolean + report |
| Vulnerability remediation tickets | s25 (postmortem tracking) | Issue list |
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.
- 12d ago First seen · 510 lines · 124 tokens per session scan A 633f1a9d717b
security-scanning is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 124 tokens to every session and 3,730 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…