TypingMindTypingMindThe best frontend for AI
Update Threat Db logo

Update Threat Db

CommunityPopular
FlorianBruniaux
update-threat-db

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.

Overview

PublisherFlorianBruniaux
Repositoryclaude-code-ultimate-guide
Skill nameupdate-threat-db
Stars
6.1K
Forks
807
Bundled files
1
LicenseCC-BY-SA-4.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by FlorianBruniaux on GitHub. Read the source before you install it.

Installation

Install the Update Threat Db AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/FlorianBruniaux/claude-code-ultimate-guide/tree/main/.agents/skills/update-threat-db
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-ultimate-guide.git /tmp/claude-code-ultimate-guide
mkdir -p .claude/skills
cp -r /tmp/claude-code-ultimate-guide/.agents/skills/update-threat-db .claude/skills/update-threat-db
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Update Threat Db in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Update Threat Db on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Update Threat Db is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

  1. Pass the AgentSec validation gates and regenerate artifacts twice without drift.
  2. Synchronize the approved public feed into the guide and landing; verify byte equality and run each consumer's integration checks.
  3. Refresh the guide's compatibility database and reader guidance only after the canonical records pass. Update each affected repository's changelog.
  4. Run python3 scripts/sync-threat-skill.py --check after editing this skill or its routing scenarios. Validate both host routes with the installed router.
  5. Report the research window, accepted and deferred records, detector limits, file changes, validation results and synchronization state.

Commit, push, tagging and publication are separate states. Follow AgentSec's authorization and data-license boundaries; a local update does not authorize a public release. State any unfinished gate explicitly.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Update Threat Db AI skill do?

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.

Why use Update Threat Db on TypingMind?

Because you install it once and use it with any model. Update Threat Db is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Update Threat Db in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FlorianBruniaux/claude-code-ultimate-guide/tree/main/.agents/skills/update-threat-db. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Update Threat Db?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Update Threat Db?

As many as you like. As long as a model supports skills, you can use Update Threat Db with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Update Threat Db AI skill free?

Yes. It is published on GitHub by FlorianBruniaux under the CC-BY-SA-4.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Openclaw Refactor Docs

openclaw
OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

82.2K
391K
Instructions
View
openclaw logo

Openclaw Repair Sweep

openclaw
OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

82.2K
391K
1 files
View
openclaw logo

Openclaw Test Performance

openclaw
OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

82.2K
391K
1 files
View
openclaw logo

Openclaw Testing

openclaw
OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

82.2K
391K
2 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇