agentsclimarketplace
Sign in

Security

Skill menot-you/n-soul/skills/security

Model trust boundaries, trace untrusted input to privileged actions, harden controls, and verify fail-closed behavior.From its SKILL.md

Install
npx -y skills add menot-you/n-soul --skill security

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 371 tokens by cl100k_base, as published. Nobody here has run it

Security

Use for auth, identity, secrets, untrusted input, network exposure, data mutation, migrations, infrastructure, release, or destructive actions.

Inputs to lock

  • Assets and security goals.
  • Actors, identities, trust boundaries, and entry points.
  • Privileged actions and data stores.
  • Current controls, failure history, and accepted risk.
  • Authority and rollback for any change.

Method

  1. Draw the data and authority flow across every trust boundary.
  2. Enumerate attacker-controlled inputs, credentials, tokens, files, messages, and network paths.
  3. Trace each input to a privileged sink. Record validation, authorization, isolation, logging, and rate limits along the path.
  4. Identify abuse cases: privilege escalation, confused deputy, replay, injection, path escape, unsafe deserialization, race, resource exhaustion, and secret disclosure.
  5. Confirm least privilege, explicit allow rules, secure defaults, bounded resources, and fail-closed behavior when dependencies are missing.
  6. Bind approval to the exact candidate and prevent substitution between review and the action.
  7. Keep secrets out of command lines, logs, generated artifacts, and durable handoffs.
  8. Add negative tests at each boundary and prove denied actions cause no state change.
  9. Verify audit records are useful without leaking sensitive data.
  10. Define rollback, recovery, and post-action readback before high-impact action.

Findings

For every finding include asset, entry point, broken control, privileged-action sink, realistic impact, proof, and a clean remediation. Rank severity from demonstrated reach and preconditions, not alarm language.

Do not approve a high-impact action while identity, candidate binding, rollback, or independent verification remains ambiguous. Surface one real blocker and one safe next action; never bury security uncertainty in a long option list.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most security skills give in 371 tokens

Counted across 666 of the 889 authors here whose files we hold, read 2026-09-06

  • Use parameterized queries for database accessin 82 of 666, across 79 files
  • Hash passwords with BCryptin 55 of 666, across 39 files
  • Implement rate limiting for public endpointsin 48 of 666, across 34 files
  • Use environment variables for secretsin 35 of 666
  • Scan dependencies for vulnerabilitiesin 35 of 666, across 24 files
  • Validate and sanitize all user inputin 35 of 666, across 32 files
  • Add security headers to all responsesin 34 of 666, across 20 files
  • Validate all external input at the system boundaryin 26 of 666, across 25 files
  • Use parameterized queries to prevent SQL injectionin 25 of 666, across 13 files
  • Store secrets in Vault or environment variablesin 25 of 666, across 10 files
  • Run containers as a non-root userin 21 of 666, across 18 files
  • Validate all input using Bean Validationin 19 of 666, across 5 files

Said here and by no other author read

  • Draw data and authority flow across trust boundaries
  • Enumerate all attacker controlled inputs
  • Trace inputs to privileged sinks
  • Identify potential abuse cases
  • Confirm least privilege and secure defaults
  • Bind approval to the exact candidate

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.