triage-security-assessment
Skill18 starsChanged 29 days agoLicence not identifiedView on GitHub
User-facing triage of an existing threat model — an overview-first console over an already-generated threat-model.yaml (backlog by priority, severity mix, worst-case scenarios), then one of three modes. "Just look around" browses findings read-only by severity, security aspect, requirement, or control posture. "Fix or accept findings now" applies the code fix for findings you pick — or accepts the risk instead — one at a time for review. "Build a remediation plan" decides mitigate / accept-risk per finding and emits a remediation-plan.md without code changes. Within a session you can also discuss a single finding by id (F-/T-/M-/W-), a read-only aside that changes nothing. Runs later and independently of appsec-analyzer; reads the model, never regenerates or re-scores it. Not an artifact-quality check (that is eval-security-assessment). To only *ask* about the model without acting on it, use ask-security-assessment.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abuse-casesSkill
- analyze-threatsSkill
- appsec-analyzerSkill
- ask-security-assessmentSkill
- audit-security-requirementsSkill
- authnz-reviewSkill
- check-permissionsSkill
- clean-run-stateSkill
- diagnose-bundleSkill
- diagnose-runSkill
- eval-security-assessmentSkill
- export-security-assessmentSkill
- fix-run-issuesSkill
- helpSkill
- install-baselineSkill
- internal-threat-analysis-kernelSkill
- remove-baselineSkill
- repo-profileSkill
- report-errorSkill
- security-assessment-healthSkill
- security-scoreSkill
- setup-targetSkill
- show-security-assessmentSkill
- statusSkill
- update-baselineSkill
- verify-baselineSkill
- verify-requirementsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 2 are distinctive, and 13 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.