Research new security advisories for coding agents and MCP, the protocol connecting agents to tools. Update AgentSec Triage records with source evidence and regression tests, then validate generated artifacts and synchronize the approved feed with dependent guides and pages.
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.
Review the instructions the agent will receive before you install.
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.
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.
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.
python3 scripts/sync-threat-skill.py --check after editing this skill or
its routing scenarios. Validate both host routes with the installed router.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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.