security-policy
Skill4 starsChanged 30 days agoMITView on GitHub
Apply the organization's secure development policy. Use when writing a spec or plan, handling authentication, secrets, cryptography, file uploads, external input, third-party dependencies, or any data classified as confidential or personal.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nanxiaoyao/network-huawei-skillstheir own version, first seen Aug 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nanxiaoyao/network-huawei-skills★ 2same name
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.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- brand-guidelinesSkill
- compliance-policySkill
- intent-templateSkill
- secure-api-reviewSkill
- ux-standardsSkill
- brand-guidelinesSkill
- compliance-policySkill
- intent-templateSkill
- secure-api-reviewSkill
- security-policySkill
- ux-standardsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 13
Secrets: never in code, config files or logs.
- Very specific: line 14
Dependencies: only from <approved registries>.
- Very specific: line 16
Cryptography: use <approved library>; no custom crypto.
≈ “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
Secure development policy
Owner: <CISO delegate> · Source of truth: <link to the security policy> · Policy version: <x.y>
<!-- TEMPLATE: replace each rule with your organization's policy text, keeping one rule per line. -->Rules
- Secrets: never in code, config files or logs. Read them from
<secret manager>. - Dependencies: only from
<approved registries>; no new dependency without a licence and vulnerability check (<tool>); never bump versions the platform team owns. - Cryptography: use
<approved library>; no custom crypto; minimum<TLS 1.2 / AES-256 / ...>. - Data classification:
<public | internal | confidential | restricted>. Restricted data stays in<approved stores>and is encrypted at rest. - External input: validate at the boundary; parameterized queries only; no shell interpolation of user input.
- Logging: log security events (auth failures, permission denials) without personal data.
- Threat model: changes that add a new trust boundary need a short threat model in
spec.md.
When writing a spec or plan
List each rule the change touches and how it is satisfied. Where two rules or two policies conflict, do not choose: record it under Areas of concern and name this policy's owner.
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.