agentleFS
vcompagnuccivcompagnucci/skills/agent-security/SKILL.md

agent-security

Skill0 starsChanged 20 days agoNo licenceView on GitHub

Secure any AI agent that reads untrusted text and calls tools, customer-facing ones included. Use for threat models, prompt injection in anything the agent reads (tickets, emails, documents, web pages, repos, tool results, pasted text), a person in the chat claiming authority or identity (impersonation, account recovery, system-prompt extraction), pressure on a customer-facing agent (refund or price bait, jokes, impossible requests), tool permissions and credentials, approvals, sandboxing and network egress, guardrail classifiers and how they stack, data exfiltration and memory poisoning, MCP servers and skills, choosing a model by attack resistance, and incident response.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use secrets-management.

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.
  • xfstudioSkill

    secrets-management

    Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — 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 7 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.