security
Skill2 starsChanged 4 months agoMITView on GitHub
When to use: Any code touching authentication, user input, external APIs, or sensitive data. Context-dependent — there is no universal "escape": If your code integrates with LLMs:
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 100 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 23
Check: type, length, format, range, encoding
- Distinctive: line 25
Prefer allowlists (define what's valid) over denylists (define what's invalid)
- Distinctive: line 42
Never in source code, never in git history
- Distinctive: line 56
If your code integrates with LLMs:
“Common” is measured: kept by at least 6 in 10 of the 100 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.
Files
Security Skill
When to use: Any code touching authentication, user input, external APIs, or sensitive data.
OWASP Top 10 cheat sheet
| # | Category | One-line check |
| A01 | Broken access control | Is authz checked at the endpoint boundary, not just the UI? |
| A02 | Crypto failures | Any weak algorithms (MD5, SHA1 for passwords)? Plaintext sensitive data? |
| A03 | Injection | Is every query parameterized? Any string interpolation into SQL/commands? |
| A04 | Insecure design | Was there a threat model? Or just hoping for the best? |
| A05 | Misconfiguration | Debug mode off in prod? Default credentials removed? CORS restrictive? |
| A06 | Vulnerable components | Dependencies audited for CVEs? |
| A07 | Auth failures | Session fixation possible? Password policy enforced? |
| A08 | Data integrity | Updates signed? CI inputs trusted? |
| A09 | Logging failures | Security events logged? PII NOT logged? |
| A10 | SSRF | Outbound requests validated? DNS rebinding mitigated? |
Input validation patterns
- Validate at the boundary — first point where external data enters your system
- Check: type, length, format, range, encoding
- Reject early — don't process invalid input hoping it works out
- Prefer allowlists (define what's valid) over denylists (define what's invalid)
Output encoding
Context-dependent — there is no universal "escape":
| Context | Encoding |
| HTML body | HTML entity encode (<, >, &) |
| HTML attribute | Attribute encode + quote the attribute |
| JavaScript | JS string encode, or use JSON.stringify |
| SQL | Parameterized queries (not escaping) |
| URL | URL encode (encodeURIComponent) |
Secret management
- Environment variables or secret manager (Vault, AWS SSM, GCP Secret Manager)
- Never in source code, never in git history
- Rotate immediately on any leak — investigate after
- Different secrets per environment
- Short-lived tokens preferred over long-lived API keys
PII handling
- Redact in logs (emails, names, addresses, phone numbers, SSNs)
- Encrypt at rest in databases
- Minimize collection — don't store what you don't need
- Audit access — who can query PII and when
Prompt injection defense
If your code integrates with LLMs:
- User input is data, not instructions — never interpolate it into system prompts
- Separate system instructions from user content with clear delimiters
- Validate LLM output before acting on it (especially tool calls)
- Log LLM interactions for forensic reconstruction
Other versions122 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 122
- BuilderIO/agent-native★ 7.4ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- gridaco/grida★ 2.7ksame name
- static-web-server/static-web-server★ 2.4ksame name
- BankrBot/skills★ 1.2ksame name
- BankrBot/openclaw-skills★ 1.2ksame name
- alinaqi/maggy★ 711same name
- alinaqi/claude-bootstrap★ 708same name
112 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use cost-reducer, albert-dm and 10 more.
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.
huyvpSkillcost-reducer
Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.
Also in 12 projects that use this
vikneshwaran16032005-altSkillalbert-dm
Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).
Also in 6 projects that use this
- vikneshwaran16032005-altSkill
new-client-system
Scaffold a new client's full stack — Next.js 16 frontend dashboard + Trigger.dev backend worker — from the Shiney automations template. Use when the user says "new client", "onboard a client", "scaffold a client system", "set up <client-name>", or wants to start a fresh frontend+backend project styled and structured like the Shiney automations dashboard. Produces structure only; no automations are scaffolded — those are added later.
Also in 6 projects that use this
ffsshhttiikkSkillscalability
Core foundational concepts and principles for Scalability
Also in 11 projects that use this
xfstudioSkilltrigger-dev
Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.
Also in 11 projects that use this
- xfstudioSkill
customer-support
Elite AI-powered customer support specialist mastering
Also in 12 projects that use this
- +4 more from vikneshwaran16032005-alt
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/paw.mdcCursor rule
- architectureSkill
- devils-advocateSkill
- frontendSkill
- git-safetySkill
- php-laravelSkill
- quality-gateSkill
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
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.