security-and-hardening
Skill8 starsChanged 4 days agoMITView on GitHub
Use when the change touches auth, secrets, audited state, audit trails, infrastructure, or external inputs — treat security as a design constraint, not final polish.
93 other projects use a version of this.
Adopted by
Most recently taken up by
- zademy/lu-querytheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- Alter-ai/skill-labtheir own version, first seen Nov 15, 2026
- fabioc-aloha/Alex_ACT_ONEtheir own version, first seen Nov 15, 2026
- tkbk-online/skillstheir own version, first seen Nov 15, 2026
- ontology-of-everything/handy-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use constraint-driven-development, observability-and-instrumentation and 8 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.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 17 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 37 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 41 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 40 projects that use this
seikaikyoSkillinterview-me
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
Also in 35 projects that use this
dariia-mSkillanti-hallucination
ALWAYS activate this skill. Apply these rules to every task regardless of domain. This skill governs how Claude Code verifies information, writes code, references documentation, and avoids fabricating functions, arguments, APIs, file paths, data structures, or facts. These rules override any inclination to guess.
Also in 3 projects that use this
- +1 more from HK-hub
Other versions93 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 93
- addyosmani/agent-skills★ 118ksame name
- penpot/penpot★ 62ksame name
- ollaya-dev/ollaya★ 1.4ksame name
- shashankswe2020-ux/whoop-mcp★ 181same name
- enes-alatas/spool★ 48same name
- vinvcn/addyosmani-agent-skills-zh★ 46same name
- jmxt3/gitscape.ai★ 33same name
- sampleXbro/agentsmesh★ 27same name
- jaskirat1616/grok-skills★ 22same name
- ishandutta2007/Awesome-Agent-Skills★ 21same name
83 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.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- batch-fixSkill
- brainstormingSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- context-engineeringSkill
- fixSkill
- handoffSkill
- implementSkill
- incremental-implementationSkill
- instructionsSkill
- lessonsSkill
- mtk-doctorSkill
- mtk-setupSkill
- mtkSkill
- planning-and-task-breakdownSkill
- pre-commit-reviewSkill
- prior-work-checkSkill
- promote-lessonSkill
- repo-healthSkill
- research-contextSkill
- setup-auditSkill
- setup-bootstrapSkill
- setup-refreshSkill
- spec-drift-detectionSkill
- spec-driven-developmentSkill
- subagent-implementationSkill
- tech-stack-dotnetSkill
- tech-stack-pythonSkill
- tech-stack-typescriptSkill
- verification-before-completionSkill
- workflow-artifactsSkill
- writing-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 88 edited versions we read keep these.
10
Distinctive
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
- Distinctive: line 25
Treat security and compliance as design constraints, not final review polish.
- Very specific: line 39
Read the domain and security supplement (.claude/references/domain-finance.md, or the team's domain-<name>.md) for regulated state, …
- Very specific: line 40
Read the stack skill's ## Framework Patterns for framework-level auth and validation idioms.
- Distinctive: line 45
Check auth and authorization requirements.
- Distinctive: line 46
Check PII, secrets, and logging behavior.
- Distinctive: line 47
Check audit requirements for state changes that require an audit trail.
- Distinctive: line 48
Check query safety, transaction boundaries, and error exposure.
- Distinctive: line 51
If a requirement is unclear, stop and ask rather than guessing.
- Distinctive: line 55
No secrets in code or logs.
- Distinctive: line 56
No unaudited state mutation where the domain requires audit trails.
- Distinctive: line 57
No trust in external input without validation.
- Distinctive: line 58
No wildcard IAM/resource access without explicit justification.
- Very specific: line 59
No new third-party dep that fails the six-criteria intake gate (.claude/references/dependency-intake-checklist.md).
“Common” is measured: kept by at least 6 in 10 of the 88 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 And Hardening
Active Stack
echo "--- Tech Stack ---"
cat .claude/tech-stack 2>/dev/null || echo "(not set)"Overview
Treat security and compliance as design constraints, not final review polish. Changes to serious software must preserve confidentiality, integrity, auditability, and least privilege.
When To Use
- Auth or authorization changes; secrets or configuration changes
- Audited state mutations (e.g. financial state, patient records, legal documents — see domain supplement)
- New endpoints, external integrations, infrastructure, or IAM changes
When NOT To Use
- Purely internal non-sensitive refactors with no new data flow or boundary change
Workflow
- Read the domain and security supplement (
.claude/references/domain-finance.md, or the team'sdomain-<name>.md) for regulated state, sensitive data, audit invariants and review questions. - Read the stack skill's
## Framework Patternsfor framework-level auth and validation idioms. - Identify trust boundaries:
- user input
- external service input
- internal privileged operations
- Check auth and authorization requirements.
- Check PII, secrets, and logging behavior.
- Check audit requirements for state changes that require an audit trail.
- Check query safety, transaction boundaries, and error exposure.
- For infra, check least privilege, blast radius, and secret access scope.
- Supply chain — dependency intake. If the diff adds or replaces a third-party dep (any of
package.json,*.csproj,Directory.Packages.props,requirements.txt,pyproject.toml,Pipfile,go.mod,Cargo.toml,Gemfile,composer.json), walk the new dep through.claude/references/dependency-intake-checklist.md— scope, maintenance, size, security, license. TwoPoorratings block; onePoorrequires written override. Cite concrete evidence (CVE id, last-release date, license SPDX) per Poor rating. - If a requirement is unclear, stop and ask rather than guessing.
Rules
- No secrets in code or logs.
- No unaudited state mutation where the domain requires audit trails.
- No trust in external input without validation.
- No wildcard IAM/resource access without explicit justification.
- No new third-party dep that fails the six-criteria intake gate (
.claude/references/dependency-intake-checklist.md).
Verification
- Trust boundaries were identified
- Auth/authz expectations were checked
- Audit requirements were checked (domain supplement consulted if present)
- No secrets or PII leakage is introduced
- Infra permissions remain least-privilege
- Any new third-party dep cleared the intake checklist (or has documented override)
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.

