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/nvsecurity/nightvision-skills/ci-cd-integrationnpx skills add nvsecurity/nightvision-skills --skill ci-cd-integrationgit clone --depth 1 https://github.com/nvsecurity/nightvision-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/nvsecurity/nightvision-skills/ci-cd-integration)<a href="https://agentmods.dev/skills/nvsecurity/nightvision-skills/ci-cd-integration"><img src="https://agentmods.dev/badge/skills/nvsecurity/nightvision-skills/ci-cd-integration.svg" alt="Measured on agentmods" 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.00078 | $0.02679 |
| Opus 5 | $0.00039 | $0.01340 |
| Sonnet 5 | $0.00016 | $0.00536 |
| Haiku 4.5 | $0.00008 | $0.00268 |
Grade A, and why
ci-cd-integration scanned grade A with 2 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 6d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo mv nightvision /usr/local/bin/ Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -L https://downloads.nightvision.net/binaries/latest/nightvision_latest_linux_amd64.tar.gz | tar -xz How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NightVision CI/CD Integration
Use this skill when helping users add NightVision security scanning to their CI/CD pipelines. NightVision is a white-box-assisted DAST tool that finds exploitable vulnerabilities in web applications and REST APIs. It combines API Discovery (static analysis to extract OpenAPI specs from source code) with dynamic scanning (ZAP + Nuclei engines), and traces vulnerabilities back to exact source code locations (Code Traceback).
Agent workflow
When a user asks to set up NightVision in their pipeline:
- Check prerequisites — verify the NightVision CLI is available (
nightvision --help). If not installed, see the Installation section below. - Examine the repo — look for existing CI configs (
.github/workflows/,.gitlab-ci.yml,Jenkinsfile,bitbucket-pipelines.yml,azure-pipelines.yml) to understand the CI platform and existing pipeline structure - Ask the user what you can't determine from the repo:
- Target URL (staging/production endpoint to scan)
- Target type — web app or API?
- Does the app require authentication to scan?
- What language is the backend? (needed for API Discovery)
- Have they already created a NightVision project, target, and token?
- Tell the user what they must do locally — some steps require interactive browser sessions that the agent cannot perform (see Prerequisites below)
- Generate the pipeline config — adapt the patterns below and the platform-specific examples in references/ci-platforms.md to the user's repo, substituting their target name, language, app startup method, and CI platform conventions
Related skills: Use scan-configuration for detailed target/auth setup, api-discovery for spec extraction details, scan-triage for interpreting results.
Pipeline structure
Every NightVision CI pipeline follows this pattern:
1. Install the NightVision CLI
2. Extract API spec from source code (API targets only)
3. Start the application (private/local targets only)
4. Run the scan (CLI polls until completion, ~5-15 min)
5. Export results (SARIF / CSV / GitLab DAST)
6. Upload to CI platform (GitHub Security, GitLab DAST, Azure Boards, Jenkins Warnings)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 233 lines · 78 tokens per session scan A 6150c3aade1f
ci-cd-integration is a skill published in the GitHub repository nvsecurity/nightvision-skills (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 2,679 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.