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 hamzabellouch/agent-skills --skill sast-dast-security-pipelinesgit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/sast-dast-security-pipelines)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/sast-dast-security-pipelines"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/sast-dast-security-pipelines/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/hamzabellouch/agent-skills/sast-dast-security-pipelines"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/sast-dast-security-pipelines.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.00052 | $0.02413 |
| Opus 5 | $0.00026 | $0.01207 |
| Sonnet 5 | $0.00010 | $0.00483 |
| Haiku 4.5 | $0.00005 | $0.00241 |
Grade A, and why
sast-dast-security-pipelines 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 8d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAST & DAST Automated Security Pipelines
Overview
This skill defines production patterns for orchestrating automated SAST, DAST, SCA, and Secret Scanning engines inside CI/CD workflows. It establishes strict vulnerability SLA enforcement, standardized SARIF (Static Analysis Results Interchange Format) ingestion into GitHub Security Hub/DefectDojo, and automated deployment blocking for non-compliant security builds.
1. DevSecOps Pipeline Architecture & Principles
- Shift-Left Continuous Analysis: Execute fast, lightweight SAST and Secret Scanning on every pull request; defer heavy DAST and full dynamic fuzzing to staging environment deployment gates.
- Standardized SARIF Telemetry: All scanners (Semgrep, Trivy, Bandit, OWASP ZAP) must output findings formatted in standard SARIF v2.1.0 to enable centralized triage and correlation.
- Zero Security Debt SLA Enforcement: Fail builds automatically if open vulnerabilities breach SLA time-to-remediate windows:
- Critical: 0-day SLA (Immediate block)
- High: 7-day SLA
- Medium: 30-day SLA
- Governed False Positive Exclusions: Code inline suppressions (
#nosec,//nolint) require peer security architect code review and mandatory expiry annotations.
2. Security Pipeline Scanning Matrix & Quality Gates
| Pipeline Stage | Security Scanner | Target Focus | Gate Action |
|---|---|---|---|
| Commit / PR | Trufflehog / Gitleaks | Hardcoded API keys, RSA keys, AWS access tokens | Block Commit |
| PR Build | Semgrep / SonarQube | Code injection, XSS, insecure deserialization, cryptographic weaknesses | Block PR Merge if High/Critical |
| Artifact Build | Trivy / Grype | Base image OS packages, application lockfiles | Block Image Push if High/Critical |
| Deploy Staging | OWASP ZAP / Nuclei | Runtime headers, CORS misconfiguration, SQLi, Auth bypass, SSRF | Block Prod Deployment |
3. Anti-Patterns & Risk Vectors
- Anti-Pattern: Ignoring DAST Authentication State
- Risk: DAST scanners running without valid session tokens or API auth headers test only unauthenticated public splash screens, missing internal microservice vulnerabilities.
- Remediation: Pass ephemeral OAuth/Bearer tokens or OpenAPI/Swagger definitions to DAST engine scans.
- Anti-Pattern: Silent / Non-Blocking CI Security Jobs (
continue-on-error: true)- Risk: Security scans run purely as cosmetic checks while critical findings flow into production unnoticed.
- Remediation: Enforce hard build failures on critical findings unless an explicit, signed security waiver exists.
- Anti-Pattern: Monolithic Unfiltered Scanning
- Risk: Scanning third-party vendor code (
node_modules/,vendor/) generates massive noise and inflates CI execution time. - Remediation: Scope path configurations to first-party source files using explicit include/exclude patterns.
- Risk: Scanning third-party vendor code (
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.
- 8d ago First seen · 259 lines · 52 tokens per session scan A 01b86e733e41
sast-dast-security-pipelines is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,413 once invoked, about $0.0003 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-09-03.
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.
tdd-configure-ci
Configures CI/CD pipelines to mechanically enforce CONSTRAINTS.md quality bars and Floor-Guard anti-cheat rules. (Optional Utility).
github-actions-patterns
Production-grade GitHub Actions workflows — reusable workflows, OIDC cloud auth, caching, matrix builds, and environment protection rules. Use when the user creates, reviews, or debugs CI/CD pipelines in .github/workflows, or asks about GitHub Actions deployment, OIDC authentication, or workflow optimization.
build-optimization
Optimize CI build speed — Docker layer caching, dependency caching, multi-stage builds, parallelism, and build matrix strategies.
gitlab-ci-patterns
GitLab CI/CD pipelines — include templates, environments, OIDC auth, caching, protected runners, deployment gates.
pipeline-security
Secure CI/CD pipelines with keyless signing, OIDC federation, provenance attestations, policy enforcement, and hardened runners.