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 mizukaizen/hive-doctrine-mcp --skill vulnerability-assessmentgit clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcpWrote 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/mizukaizen/hive-doctrine-mcp/vulnerability-assessment)<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.
<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>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.00000 | $0.00590 |
| Opus 5 | $0.00000 | $0.00295 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
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.
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
/scancommand is invoked - User asks "is this code secure?" or "what are the security risks?"
Process
-
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)
-
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
-
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?)
-
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]
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.
- 11d ago First seen · 71 lines · 0 tokens per session scan A 1427f2e37e67
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.
Other skills, from other repositories
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
brain-in-the-fish
Universal document evaluation engine — evaluate any document against any criteria using cognitively-modelled AI agents with ontology-grounded scoring.
superagenticmcp
SuperAgenticMCP — the switchboard for your agent swarm. MCP-native router and multi-agent control plane that plans tasks, routes tool calls to racked MCP servers by capability and latency, streams execution, and files results into a memory-scope graph. Use when the user needs multi-agent orchestration over MCP, a…
go-best-practices
Go coding best practices. Use when writing or reviewing Go code. Covers error handling, concurrency, and idiomatic patterns.
typescript-best-practices
TypeScript/Node.js best practices. Use when writing or reviewing TypeScript code. Covers type safety, async patterns, and error handling.
multi-agent-governance
Use this skill when building, managing, or auditing multi-agent AI systems. Provides governance patterns for behavioral enforcement, drift detection, audit trails, role management, and accountability across autonomous AI agents. Compatible with any orchestration framework.