update-threat-db

update-threat-db is a command for Claude Code from FlorianBruniaux/claude-code-ultimate-guide. It costs 0 tokens per session (462 once invoked), scanned A, original, CC-BY-SA-4.0.

A command for AgentSec Triage, described as the technical source for threat evidence, dated fiches, detector inputs, and a public security feed. The available description does not explain its exact operation.

In plain words
What is it for?
Use it when working with AgentSec threat evidence or the guide database; further capabilities are not specified here.
Why use it?
It is intended to keep security-guide work based on the canonical threat database instead of unverified research or manual edits.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/test-check-agentsec-security-feed.py.

Good fit Use it when working with AgentSec threat evidence or the guide database; further capabilities are not specified here.

Compare 6 commands from other repositories ↓
About the project

Claude Code Ultimate Guide is a structured documentation project for learning how to build, operate, and govern coding agents with Claude Code. It serves developers and teams through guidance on agentic workflows, hooks, skills, MCP servers, security, and adoption. The catalogue entries are reusable skills, commands, agents, hooks, instructions, settings, and a plugin drawn from the guide's workflow materials.

FlorianBruniaux/claude-code-ultimate-guide · 5,909 stars · on GitHub · cc.bruniaux.com

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

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

Made for: Claude Code.

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-ultimate-guide/update-threat-db.svg)](https://agentmods.dev/commands/florianbruniaux/claude-code-ultimate-guide/update-threat-db)
Your own site
<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-ultimate-guide/update-threat-db"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-ultimate-guide/update-threat-db.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 462 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 unknown 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.00462
Opus 5 $0.00000 $0.00231
Sonnet 5 $0.00000 $0.00092
Haiku 4.5 $0.00000 $0.00046

Measured 8d ago against content hash 6296e6a6f165, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 8d 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.

.claude/commands/update-threat-db.md · 55 lines

The source is not reproduced here

Licensed CC-BY-SA-4.0

The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 8d ago First seen · 55 lines · 0 tokens per session scan A 6296e6a6f165

Subscribe to this mod's changes

update-threat-db is a command published in the GitHub repository FlorianBruniaux/claude-code-ultimate-guide (5,909 stars, last pushed yesterday), licensed CC-BY-SA-4.0. It costs nothing until one of its globs matches a file; then it loads 462 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-30.

Related

Other commands, from other repositories