agentleFS
Sign inStart free
dRafaleDdRafaleD/cybersec-skills/skills/application/lean-crypto/SKILL.md

lean-crypto

Skill2 starsChanged 55 days agoMITView on GitHub

Runs token-efficient defensive cryptography reviews for Cursor and Codex. Inventories weak hashes, ECB mode, Math.random tokens, and hardcoded IVs in local code, then reports compact algorithm and key-handling fixes. Use when the user asks for crypto review, TLS, hashing, JWT signing, RNG, or password storage. Do not use for cracking hashes, forging tokens, or designing novel ciphers.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

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

    Default lean. deep only if asked.

    line 28
  2. Very specific:

    Run weak. Queue MD5/SHA1 for security, DES/ECB, Math.random for tokens, static IVs, verify=False.

    line 38
  3. Distinctive:

    No hash cracking, rainbow tables, or token-forging steps.

    line 44
  4. Very specific:

    No secret values. [REDACTED] for keys.

    line 45
  5. Distinctive:

    Do not invent custom crypto.

    line 46

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

Lean Crypto

Defensive crypto hygiene in this workspace. Scripts list weak primitives; you confirm a few files; you patch only when asked.

Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.

python3 "$SKILL_ROOT/scripts/lean_crypto.py" weak .
python3 "$SKILL_ROOT/scripts/lean_crypto.py" trim --chars 2500 path/to/out.txt

Mode

Default lean. deep only if asked.

ModeBudget
leanweak + up to 8 slices; references/primitives.md; ≤6 findings
standard+ references/keys.md; up to 16 slices; ≤10 findings
deepneeded refs only; ≤16 findings

Workflow

  1. Run weak. Queue MD5/SHA1 for security, DES/ECB, Math.random for tokens, static IVs, verify=False.
  2. Slice-read the matching file. Cap quotes at 12 lines.
  3. Report the safer primitive. Stop unless asked to patch.

Hard rules

  • No hash cracking, rainbow tables, or token-forging steps.
  • No secret values. [REDACTED] for keys.
  • Do not invent custom crypto. Prefer platform libraries.

Report template

## Lean-crypto (`<mode>`)

**Scope:** <app> | **Budget:** files_read=<n>

| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| HIGH | file:line | MD5 for passwords | Argon2id or bcrypt |

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