agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/security-assistant/SKILL.md

security

Skill4 starsChanged 29 days agoMITView on GitHub

Guide security review and vulnerability assessment following OWASP standards. Use when: security audit, vulnerability check, secure coding review, threat modeling. Not for: automated dependency, CVE, and secret scanning — use /scan; handling a breach in progress — use /incident. Keywords: security, OWASP, vulnerability, authentication, authorization.

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use albert-dm, cost-reducer and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yawningwhaleAISkill

    albert-dm

    Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).

    Also in 5 projects that use this

  • huyvpSkill

    cost-reducer

    Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.

    Also in 11 projects that use this

  • yawningwhaleAISkill

    new-client-system

    Scaffold a new client's full stack — Next.js 16 frontend dashboard + Trigger.dev backend worker — from the Shiney automations template. Use when the user says "new client", "onboard a client", "scaffold a client system", "set up <client-name>", or wants to start a fresh frontend+backend project styled and structured like the Shiney automations dashboard. Produces structure only; no automations are scaffolded — those are added later.

    Also in 5 projects that use this

  • xfstudioSkill

    trigger-dev

    Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

    Also in 10 projects that use this

  • ffsshhttiikkSkill

    scalability

    Core foundational concepts and principles for Scalability

    Also in 11 projects that use this

  • h-mascotSkill

    self-healing

    Wrap long-running or fragile OpenClaw work in checkpointed retries, watchdogs, fallback models, and proof-of-completion so failed subagents can resume instead of silently dying.

    Also in 11 projects that use this

  • +3 more from yawningwhaleAI

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 108 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After /security completes, the AI assistant should suggest:

    line 79

“Common” is measured: kept by at least 6 in 10 of the 108 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Security Assistant | 安全審計助手

Guide systematic security reviews following OWASP Top 10 and industry best practices.

引導系統化的安全審查，遵循 OWASP Top 10 和業界最佳實踐。

Quick Checklist — OWASP Top 10 Prevention | 快速檢查清單

IDRiskPrevention預防措施
A01Broken Access ControlEnforce least privilege, deny by default最小權限原則，預設拒絕
A02Cryptographic FailuresUse strong algorithms, protect keys使用強加密演算法，保護金鑰
A03InjectionParameterized queries, input validation參數化查詢、輸入驗證
A04Insecure DesignThreat modeling, secure design patterns威脅建模、安全設計模式
A05Security MisconfigurationHardened defaults, minimal permissions強化預設值、最小權限
A06Vulnerable ComponentsTrack dependencies, patch regularly追蹤相依套件、定期修補
A07Auth FailuresMFA, strong password policies多因素認證、強密碼策略
A08Data Integrity FailuresVerify signatures, use trusted sources驗證簽章、使用可信來源
A09Logging FailuresLog security events, monitor alerts記錄安全事件、監控告警
A10SSRFValidate URLs, restrict outbound traffic驗證 URL、限制對外流量

Security Review Workflow | 安全審查工作流程

SCOPE ──► SCAN ──► ANALYZE ──► REPORT

1. Scope — Define Audit Boundary | 定義審計範圍

Identify target modules, data flows, and trust boundaries.

識別目標模組、資料流和信任邊界。

2. Scan — Identify Vulnerabilities | 識別漏洞

Review code for OWASP Top 10 patterns, check dependencies, inspect configurations.

檢查程式碼的 OWASP Top 10 模式、檢查相依套件、檢視配置。

3. Analyze — Assess Risk | 評估風險

Classify findings by severity (Critical/High/Medium/Low) and exploitability.

依嚴重程度（Critical/High/Medium/Low）和可利用性分類。

4. Report — Document Findings | 記錄發現

Produce actionable findings with remediation recommendations.

產出可行動的發現報告，附帶修復建議。

Severity Classification | 嚴重程度分類

LevelCriteria標準
CriticalRemote code execution, data breach遠端程式碼執行、資料洩漏
HighAuthentication bypass, privilege escalation認證繞過、權限提升
MediumInformation disclosure, CSRF資訊洩漏、CSRF
LowMissing headers, verbose errors缺少 Header、冗長錯誤訊息

Usage | 使用方式

/security                - Full security review of current project | 完整安全審查
/security src/auth       - Audit specific module | 審計特定模組
/security --owasp        - OWASP Top 10 focused review | OWASP Top 10 重點審查

Next Steps Guidance | 下一步引導

After /security completes, the AI assistant should suggest:

安全審查完成。建議下一步 / Security review complete. Suggested next steps:

  • 執行 /checkin 確認修復符合提交規範 ⭐ Recommended / 推薦 — Verify fixes meet check-in standards
  • 執行 /code-review 進行程式碼審查 — Run code review on security fixes
  • 執行 /commit 提交安全修復 — Commit security fixes
  • 檢查相依套件更新 → npm audit 或 pip audit — Check dependency updates

Reference | 參考

  • Core standard: security-standards.md

Version History | 版本歷史

VersionDateChanges變更說明
1.0.02026-03-23Initial release初始版本

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/security

For complete AI agent behavior definition, see the corresponding command file: /security

License | 授權

CC BY 4.0 — Documentation content

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free