agentleFS
Sign inStart free
lgzarturolgzarturo/codeconductor/.agents/skills/security-crypto/SKILL.md

security-crypto

Skill0 starsChanged 26 days agoMITView on GitHub

Choose and review cryptographic usage in your codebase: TLS, hashing, KMS, secret storage. Prefer standard libraries and vetted constructions.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill only with explicit written authorization for a named scope (systems, environments, and time window).

    line 11
  2. Distinctive:

    Use platform TLS and KMS; do not invent protocols

    line 20
  3. Distinctive:

    Keep keys out of git; rotate on leak

    line 22
  4. Distinctive:

    Ask models to 'break' or weaken crypto for a CTF against third parties

    line 27
  5. Distinctive:

    Do not produce exploit payloads, malware, or attack procedures.

    line 29

≈ “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.

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

Applied Cryptography

Authorization

Use this skill only with explicit written authorization for a named scope (systems, environments, and time window). If authorization is missing, expired, or the request is for someone else's systems, stop.

This skill is defensive and owner-authorized. It does not authorize offensive cyber operations.

Do

  • Use platform TLS and KMS; do not invent protocols
  • Hash passwords with a memory-hard KDF; never roll your own
  • Keep keys out of git; rotate on leak

Do not

  • Recommend ECB, MD5 for security, or home-grown ciphers
  • Ask models to 'break' or weaken crypto for a CTF against third parties
  • Do not produce exploit payloads, malware, or attack procedures.

How to Use

Load this skill from /cc-security when the Task Card domain is security-crypto. Example prompts:

  • Review how we store refresh tokens. Propose KMS envelope encryption and tests.
  • Replace SHA-1 password hashes in this legacy module with a modern KDF and a migration plan.

Integration

  • Workflow: /cc-security (CCEP command security)
  • Existing OWASP application-security skill remains security (not this id)
  • High-risk changes still require security-reviewer

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