# Update Threat Db

Update the guide's threat intelligence through AgentSec Triage, research new...

- Repository: https://github.com/FlorianBruniaux/claude-code-ultimate-guide (6315 stars)
- Category: Security
- License: CC-BY-SA-4.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill update-threat-db -g -a claude-code -y`
Codex: `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill update-threat-db -g -a codex -y`
Cursor: `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill update-threat-db -g -a cursor -y`
Gemini CLI: `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill update-threat-db -g -a gemini-cli -y`

## Description

Update the guide's threat intelligence through AgentSec Triage, research new coding-agent and MCP security advisories, and synchronize the security feed. Use for threat database refreshes or mise a jour de la base de menaces, not repository security scans or Claude Code release tracking.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Update threat intelligence through AgentSec

Scope: this guide repository and its AgentSec and landing consumers. This skill
does not change global agent configuration. Its canonical source is
`.claude/skills/update-threat-db/`; regenerate the Codex projection with
`python3 scripts/sync-threat-skill.py --write` from the guide root.

## Resolve the workflow

Read `.claude/commands/update-threat-db.md` from the guide root in full. It owns
the delegation contract and consumer checks. Resolve `AGENTSEC_REPO` if set,
otherwise the sibling `../agentsec-triage`. Verify the required files before
continuing. Do not silently substitute the guide's compatibility database.

Read the resolved AgentSec `AGENTS.md` and
`.claude/commands/update-threat-db.md` in full, then execute that workflow.
Preserve unrelated edits in all checkouts. Use the latest recorded update date
through today's date as the research window.

## Evidence and changes

Review primary sources before accepting new records. Keep the evidence sources,
dated events, exact detector inputs and public feed as separate artifacts. Record
affected ranges, fixed versions and uncertainty only when the source supports
them. Deduplicate CVE/GHSA aliases. Keep corrections as dated events.

Add the required regression test before each accepted data change. Distinguish
`detected`, `partial`, `not_detected` and `not_applicable`; a documented CVE does
not prove executable detection. Do not run malicious samples.

## Completion checks

The rest: https://github.com/FlorianBruniaux/claude-code-ultimate-guide/blob/HEAD/.agents/skills/update-threat-db/SKILL.md