scan-configuration

scan-configuration is a skill for Claude Code from nvsecurity/nightvision-skills. It costs 50 tokens per session (2,262 once invoked), scanned A, original, Apache-2.0.

A guide for preparing NightVision DAST scans. DAST, or dynamic application security testing, checks a running web app or API for security problems.

In plain words
What is it for?
Use it to create NightVision projects and targets, configure headers, cookies, or Playwright authentication, record web traffic, exclude paths, and verify scan readiness.
Why use it?
It helps remove setup gaps before scanning, such as missing targets, login details, traffic recordings, or scope exclusions. This reduces the chance of scanning the wrong parts of an application or getting unusable results.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the nightvision-skills plugin — 5 skills shipped together

Good fit Use it to create NightVision projects and targets, configure headers, cookies, or Playwright authentication, record web traffic, exclude paths, and verify scan readiness.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nvsecurity/nightvision-skills/scan-configuration
Install

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.

Any agent
npx skills add nvsecurity/nightvision-skills --skill scan-configuration
Clone the repo
git clone --depth 1 https://github.com/nvsecurity/nightvision-skills

Made for: Claude Code.

Or install nightvision-skills, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for scan-configuration

README.md
[![agentmods](https://agentmods.dev/badge/skills/nvsecurity/nightvision-skills/scan-configuration.svg)](https://agentmods.dev/skills/nvsecurity/nightvision-skills/scan-configuration)
Your own site
<a href="https://agentmods.dev/skills/nvsecurity/nightvision-skills/scan-configuration"><img src="https://agentmods.dev/badge/skills/nvsecurity/nightvision-skills/scan-configuration.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.02262
Opus 5 $0.00025 $0.01131
Sonnet 5 $0.00010 $0.00452
Haiku 4.5 $0.00005 $0.00226

Measured 9d ago against content hash 6fc38fc48a44, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

scan-configuration 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 9d 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.

skills/scan-configuration/SKILL.md · 280 lines

How it starts

The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NightVision Scan Configuration

Use this skill when helping users set up everything needed before running a NightVision DAST scan — targets, authentication, traffic recordings, projects, and scope control.

Agent workflow

When a user asks to configure a scan:

  1. Check prerequisites — verify the NightVision CLI is available (nightvision --help). Check if NIGHTVISION_TOKEN is set.
  2. Determine what exists — ask if they have a NightVision account, project, and token already. Use nightvision project list and nightvision target list -p <project> to see current state (output defaults to text; use --format json for structured parsing)
  3. Create the project (if needed) — projects organize targets, scans, and auth resources
  4. Create the target — web app or API, with the correct URL and spec
  5. Set up authentication (if needed) — determine the method and guide the user through it
  6. Record traffic (if needed) — for apps with complex workflows or dynamic identifiers
  7. Configure scope — set exclusions to avoid scanning health checks, admin endpoints, etc.
  8. Verify readiness — confirm the target is reachable and the auth works

Related skills: Use ci-cd-integration for pipeline setup, api-discovery for spec extraction, scan-triage for interpreting results.

Projects

Projects are organizational containers for targets, scans, and auth resources. They can be shared with team members.

# Create a project
nightvision project create -n my-project

# List projects
nightvision project list

# Set default project (used when -p flag is omitted)
nightvision project set -p my-project

# Share — done through the web UI at app.nightvision.net

Targets

Two types: Web (URL only) and API (URL + OpenAPI/Postman spec).

Creating targets

# Web target
nightvision target create my-web-app https://staging.example.com \
  --type WEB -p my-project

# API target with local spec file (.json, .yml, .yaml, .swagger, .postman)
nightvision target create my-api https://api.example.com \
  --type API -p my-project --spec-file openapi-spec.yml

# API target with remote spec URL
nightvision target create my-api https://api.example.com \
  --type API -p my-project --spec-url https://api.example.com/openapi.json

# Idempotent create-or-update (useful in automation)
nightvision target create my-api $URL --type API -p my-project --spec-file spec.yml \
  || nightvision target update my-api -p my-project --spec-file spec.yml

Read the full file on GitHub · 280 lines

Changes

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.

  1. 9d ago First seen · 280 lines · 50 tokens per session scan A 6fc38fc48a44

Subscribe to this mod's changes

scan-configuration is a skill published in the GitHub repository nvsecurity/nightvision-skills (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,262 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens