Coordinate threat research and updates in AgentSec, then synchronize validated results to the guide and landing page. Check compatibility data and the searchable catalogue, and report the status of each repository separately.
Delegate threat-intelligence research and updates to AgentSec, then validate the guide and landing mirrors.
Review the instructions the agent will receive before you install.
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.
agentsec-triage checkout or use AGENTSEC_REPO.AGENTS.md and
.claude/commands/update-threat-db.md completely.exports/security-feed.v1.json to the guide and landing only
after AgentSec passes locally..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.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.
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.