exec-security
Skill1 starsChanged 28 days agoMITView on GitHub
Execution skill loaded when modifying auth, API endpoints, data access, or user inputs.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- could be automatic: a setting could enforce it
- Distinctive: line 7
When touching sensitive areas of the codebase, strictly adhere to this security checklist:
- Distinctive: line 9
Input Validation: Never trust user input. Ensure all incoming data is validated and typed before processing.
- Distinctive: line 11
Authorization: Verify the user has the correct permissions (not just authentication) to perform the action or access the data.
- Distinctive: line 12
Secrets Management: Never hardcode API keys, tokens, or passwords.
- Distinctive: line 13
SQL/NoSQL Injection: Always use parameterized queries or ORM methods that automatically escape inputs.
- Distinctive: line 15
Do not merge any code that bypasses these checks.
≈ “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.
Files
Security Execution Strategy
When touching sensitive areas of the codebase, strictly adhere to this security checklist:
- Input Validation: Never trust user input. Ensure all incoming data is validated and typed before processing.
- Output Sanitization: Prevent XSS by sanitizing data before it reaches the UI.
- Authorization: Verify the user has the correct permissions (not just authentication) to perform the action or access the data.
- Secrets Management: Never hardcode API keys, tokens, or passwords. Ensure they are loaded from environment variables or secure vaults.
- SQL/NoSQL Injection: Always use parameterized queries or ORM methods that automatically escape inputs.
Do not merge any code that bypasses these checks. If you discover a pre-existing security flaw during your work, flag it immediately.
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.

