Skip to content
Back to skills

Update Threat Db

ASecurity

Delegate threat-intelligence research and updates to AgentSec, then validate the guide and landing mirrors.

  • 6,113 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
developmentdatabasesecurity

Security analysis

A100/100

Scanned October 1, 2026

npx -y skills add FlorianBruniaux/claude-code-ultimate-guide --skill update-threat-db --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Update Threat Db?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Update Threat Db
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/florianbruniaux-update-threat-db/badge)](https://www.skillsdirectory.com/skills/florianbruniaux-update-threat-db)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: update-threat-db
description: Delegate threat-intelligence research and updates to AgentSec, then validate the guide and landing mirrors.
---

# Update threat intelligence through AgentSec

AgentSec Triage owns the technical source of truth. This guide skill is a
delegator and does not carry a private copy of the threat database.

## Workflow

1. Locate the sibling `agentsec-triage` checkout or use `AGENTSEC_REPO`.
2. Read AgentSec's `AGENTS.md` and
   `.claude/commands/update-threat-db.md` completely.
3. Execute the source review, red-first tests, authoring changes, and builders
   inside an isolated AgentSec worktree.
4. Synchronize `exports/security-feed.v1.json` to the guide and landing only
   after AgentSec passes locally.
5. Follow the guide's `.claude/commands/update-threat-db.md` for compatibility
   database updates and the landing's searchable catalogue sync/check command.
   A current feed badge does not prove the catalogue contains the new records.
6. Run the guide and landing mirror checks, then report each repository's
   status separately.

Do not treat the guide's compatibility database as canonical. Do not publish,
tag, or push AgentSec while its license decision blocks public release.

The compatibility database still consumed by the guide commands is
`examples/commands/resources/threat-db.yaml`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…