vulnerability-assessment

vulnerability-assessment is a skill for Claude Code, Codex from mizukaizen/hive-doctrine-mcp. It costs 0 tokens per session (590 once invoked), scanned A, original, MIT.

A security-review skill that checks dependencies, application code, and configuration for vulnerabilities, or weaknesses attackers could exploit.

In plain words
What is it for?
Use it to review endpoints, authentication, file uploads, integrations, infrastructure, dependencies, input validation, and cryptography, then create a prioritised fix plan.
Why use it?
It helps identify security risks across the parts of a system that users, attackers, or third-party services can reach.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review endpoints, authentication, file uploads, integrations, infrastructure, dependencies, input validation, and cryptography, then create a prioritised fix plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mizukaizen/hive-doctrine-mcp/vulnerability-assessment
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 mizukaizen/hive-doctrine-mcp --skill vulnerability-assessment
Clone the repo
git clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcp

Made for: Claude Code, Codex.

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 vulnerability-assessment

README.md
[![agentmods](https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/vulnerability-assessment/github.svg)](https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/vulnerability-assessment)
Your own site
<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/vulnerability-assessment"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/vulnerability-assessment/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.

agentmods 80×15 button for vulnerability-assessment

Your own site · 80×15
<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/vulnerability-assessment"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/vulnerability-assessment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 590 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.00000 $0.00590
Opus 5 $0.00000 $0.00295
Sonnet 5 $0.00000 $0.00118
Haiku 4.5 $0.00000 $0.00059

Measured 11d ago against content hash 1427f2e37e67, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

vulnerability-assessment 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 11d 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.

gated-products/honey/claude-packages/HD-4007-security-team/skills/vulnerability-assessment/SKILL.md · 71 lines

How it starts

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

Vulnerability Assessment Skill

Use when assessing security posture. Scans dependencies, code, and configuration for vulnerabilities. Produces prioritised remediation plan.

When to Activate

  • User asks to "check security", "find vulnerabilities", or "audit for risks"
  • The /scan command is invoked
  • User asks "is this code secure?" or "what are the security risks?"

Process

  1. Identify the attack surface. What is exposed?

    • Public endpoints (APIs, web pages, webhooks)
    • Authentication boundaries (login flows, API keys, tokens)
    • Data entry points (forms, file uploads, URL parameters)
    • Third-party integrations (payment processors, auth providers, APIs)
    • Infrastructure (containers, servers, cloud services)
  2. Scan each layer.

    Dependencies:

    • Parse lock files for exact versions
    • Cross-reference against vulnerability databases
    • Identify transitive dependencies (the dependency's dependencies)
    • Note which vulnerabilities are actually reachable in your code

    Application code:

    • Review for OWASP Top 10 patterns
    • Check input validation coverage
    • Verify authentication and authorisation logic
    • Inspect cryptographic usage
    • Look for information leakage in errors and logs

    Configuration:

    • Check for secure defaults
    • Verify secrets management
    • Inspect network exposure
    • Review container security settings
  3. Score and prioritise. For each finding:

    • Assign CVSS score based on attack vector, complexity, privileges required, user interaction, scope, and impact
    • Assess exploitability in the specific context (is the vulnerable code path reachable?)
    • Consider blast radius (what else is affected if this is exploited?)
  4. Produce remediation plan. Ordered by priority:

# Remediation Plan

## Immediate (Critical — fix today)
1. [Finding] — [Fix description] — [Effort estimate]

## This Week (High)
1. [Finding] — [Fix description] — [Effort estimate]

## This Sprint (Medium)
1. [Finding] — [Fix description] — [Effort estimate]

## Backlog (Low)
1. [Finding] — [Fix description] — [Effort estimate]

Read the full file on GitHub · 71 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. 11d ago First seen · 71 lines · 0 tokens per session scan A 1427f2e37e67

Subscribe to this mod's changes

vulnerability-assessment is a skill published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 590 tokens. 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-31.

Related

Other skills, from other repositories