update-threat-db

update-threat-db is a command for coding agents from FlorianBruniaux/claude-code-plugins. It costs 14 tokens per session (1,278 once invoked), scanned A, original, MIT.

A command that researches and updates a database of security threats affecting AI agents, including vulnerabilities, malicious skills, and campaigns.

In plain words
What is it for?
Use it to inspect an existing threat database, research new threats, and add non-duplicate entries after security advisories or on a regular schedule.
Why use it?
It helps keep threat information current so security reviews are not based only on an outdated list.

Command

Part of the security-suite plugin — 2 skills, 5 commands, 2 agents shipped together

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.

agentmods
npx agentmods add commands/florianbruniaux/claude-code-plugins/update-threat-db
Clone the repo
git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-plugins

Or install security-suite, the plugin that ships this one along with the rest of its 2 skills, 5 commands, 2 agents.

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 update-threat-db

README.md
[![agentmods](https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/update-threat-db.svg)](https://agentmods.dev/commands/florianbruniaux/claude-code-plugins/update-threat-db)
Your own site
<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-plugins/update-threat-db"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/update-threat-db.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.01278
Opus 5 $0.00007 $0.00639
Sonnet 5 $0.00003 $0.00256
Haiku 4.5 $0.00001 $0.00128

Measured yesterday against content hash 72217c2bd9bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-threat-db 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 yesterday.

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.

plugins/security-suite/commands/update-threat-db.md · 171 lines

How it starts

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

Update Threat Database

Research and update the AI agent security threat intelligence database with the latest threats, CVEs, malicious skills, and campaigns.

Time: 3-8 minutes | Scope: examples/commands/resources/threat-db.yaml

Requires Perplexity MCP (or manual web search). Run monthly or after major security advisories.

Instructions

You are a threat intelligence analyst specializing in AI coding agent security. Research the latest threats and update the threat database.


Phase 1: Current State Assessment

Read the current threat database:

Read examples/commands/resources/threat-db.yaml

Note:

  • Current version and updated date
  • Number of malicious authors, skills, CVEs, campaigns
  • Most recent entries to avoid duplicates

Phase 2: Research New Threats

Run 4 targeted Perplexity searches (parallel when possible):

Search 1: New malicious skills & campaigns

Query: "malicious AI agent skills ClawHub OpenClaw skills.sh 2026 new campaigns malware supply chain"
Focus: New malicious skill names, authors, campaigns not already in threat-db.yaml

Search 2: New MCP server CVEs

Query: "MCP server CVE vulnerability 2025 2026 model context protocol security advisory"
Focus: New CVEs for MCP servers, SDK vulnerabilities, transport-level flaws

Search 3: New attack techniques

Query: "AI coding agent attack prompt injection Claude Code Cursor supply chain security research 2026"
Focus: New attack vectors, techniques, research papers

Search 4: New defensive tools & blocklists

Query: "MCP security scanner tool mcp-scan alternative AI agent skills security scanning 2026"
Focus: New scanning tools, blocklists, defensive frameworks

If Perplexity MCP is unavailable, use WebSearch for each query.


Phase 3: Analyze & Deduplicate

For each finding from Phase 2:

  1. Check if already in threat-db.yaml — skip duplicates
  2. Verify source credibility — prefer: CVE databases, security vendor blogs, peer-reviewed research
  3. Categorize — which section does it belong to?
    • malicious_authors — new confirmed malicious publishers
    • malicious_skills — new confirmed malicious skill/package names
    • malicious_skill_patterns — new prefix patterns for wildcard matching
    • cve_database — new CVEs with component, severity, fixed_in
    • minimum_safe_versions — update if new patches available
    • iocs — new C2 IPs, exfil URLs, malware hashes
    • campaigns — new coordinated campaigns
    • attack_techniques — new documented attack vectors
    • scanning_tools — new tools or major updates
    • defensive_resources — new frameworks, blocklists

Read the full file on GitHub · 171 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. yesterday First seen · 171 lines · 14 tokens per session scan A 72217c2bd9bd

Subscribe to this mod's changes

update-threat-db is a command published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 1,278 once invoked, about $0.0001 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-04.