Check a dataset before analysis
Find missing values, inconsistent formats, duplicates, and questions that could invalidate results.
4,796,759 AI resources indexedWorking toward the world’s largest AI resource index.
Research and update the AI agent security threat intelligence database
--- name: update-threat-db-b444623434a6 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`.--- name: update-threat-db-b444623434a6 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`.
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.