agentleFS
fhgomesfhgomes/my-awesome-agents-skills/skills/sentinel/SKILL.md

sentinel

Skill5 starsChanged 41 days agoGPL-3.0View on GitHub

Cybersecurity and DevSecOps infrastructure hardening specialist. Use ALWAYS when conversation involves: server security, hardening of nginx/SSH/DNS/firewall, API and endpoint protection, vulnerability or CVE analysis, CVE feed triage and backlog hygiene, secure Docker/container configuration, database protection (PostgreSQL, Redis), Spring Boot / JVM security, SSL/TLS certificates, authentication (Basic Auth, OAuth2, JWT, Keycloak), WAF, rate limiting, anti-DDoS, suspicious log analysis, incident response, ethical penetration testing, Zero Trust, secrets management, DevSecOps pipelines, or any variation of "how to protect X", "is it secure?", "how to harden Y". ALSO INCLUDES AI/LLM/autonomous agent security: prompt injection (direct and indirect), agent jailbreaking, agent hijacking, Ollama security, MCP server/token protection, agent container isolation, execution sandbox, tool permissions, denial of wallet, API key protection, data leakage via AI outputs, OWASP Top 10 for LLMs, AI supply chain, OpenClaw/agent auditing. Also trigger when user mentions: "hacker", "breach", "attack", "exposed", "brute force", "scanning", "CVE", "Trivy", "Semgrep", "fail2ban", "iptables", "UFW", "CrowdSec", "ModSecurity", "Cloudflare", "DNS exposure", "prompt injection", "jailbreak", "Ollama exposed", "MCP security", "agent security", "AI security", "LLM security", "agent security", "OpenClaw security". If there is ANY doubt whether topic is security, trigger this skill — better to consult and not need than to need and not consult.

  • Reads credentials

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

33 rules. 0 are common, 31 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 31

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 12 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.

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.