Security
Agentic Framework for Modern Development
npx -y skills add LazyIsEfficient/agentic-os --skill securityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 13 stars13 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.
What its author says it does
Copied from the file, not written here
Scan and redact PII and sensitive data (emails, phone numbers, SSNs, API keys, IP addresses, credentials, amounts, company/person names) from repository files. Includes a pre-commit hook to block commits containing PII. Use when asked to audit code for sensitive data, sanitize files before publishing, or install PII detection hooks. For application security hardening see security-engineering.
SKILL.md
2.6 KB, 363 tokens by cl100k_base, as published. Nobody here has run it
Security Sanitizer
Scans and redacts PII / sensitive data from files in this repo. Uses only Python standard library — no external dependencies.
Tools
Resolve scripts project-first, then global install (findings-ledger references/install-paths.md — same pattern, swap skill name):
PROJ="${CLAUDE_PROJECT_DIR:-.}"
SAN="$PROJ/.claude/skills/security/scripts/sanitizer.py"
[ -f "$SAN" ] || SAN="$PROJ/.agents/skills/security/scripts/sanitizer.py"
[ -f "$SAN" ] || SAN="$HOME/.claude/skills/security/scripts/sanitizer.py"
[ -f "$SAN" ] || SAN="$HOME/.agents/skills/security/scripts/sanitizer.py"
| Script | Purpose | Key Command |
|---|---|---|
scripts/sanitizer.py | Scan or redact PII in files | python3 "$SAN" --scan --dir . --recursive |
scripts/pre-commit-hook.sh | Git hook to block commits with PII | Copy it from the resolved skill directory to .git/hooks/pre-commit, then chmod +x it |
Configuration
Edit scripts/sanitizer-config.json beside this skill (same directory as $SAN) to customize blocklists, custom regex patterns, skip paths, and placeholder format.
Exit Codes
0 = clean, 1 = PII found (useful for CI).
Related skills
- security-engineering — application security, OWASP, auth hardening, input validation, auth/session patterns for web applications
Gives 0 of the 12 instructions most security skills give in 363 tokens
Counted across 648 of the 828 authors here whose files we hold, read 2026-08-07
- parameterize all database queriesin 68 of 648, across 51 files
- hash passwords using bcrypt scrypt or argon2in 49 of 648, across 36 files
- apply rate limiting to authentication endpointsin 48 of 648, across 24 files
- Configure security headersin 35 of 648, across 19 files
- validate all inputsin 32 of 648, across 24 files
- validate all external input at the system boundaryin 29 of 648, across 19 files
- run containers as a non-root userin 28 of 648, across 15 files
- use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
- run dependency audits before every releasein 21 of 648, across 10 files
- encode output to prevent cross-site scriptingin 21 of 648, across 11 files
- copy dependencies before source codein 20 of 648, across 9 files
- store secrets in environment variablesin 20 of 648, across 18 files
Said here and by no other author read
- scan files for PII
- redact PII from files
- resolve sanitizer script project-first
- edit config to customize blocklists
- install pre-commit hook to block PII
- exit with status code one when PII is found
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.