security-review
Skill3 starsChanged 9 days agoMITView on GitHub
Use before committing changes that touch authentication, authorization, secrets, audit, redaction, Odoo RPC, or request validation. Reviews secret leakage, default-deny policy, query protection, and mutation safeguards.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- Badhon-00/MDCPtheir own version, first seen Nov 16, 2026
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- metacircu1ar/hive_skillstheir own version, first seen Nov 15, 2026
- rschuft/ai-frontend-skill-packstheir own version, first seen Nov 15, 2026
- 81wallace18/codex-skillstheir own version, first seen Nov 15, 2026
- FimawLLC/fimaw-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use dependency-cve-sweep, fleet-standard-adoption 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.
berntpoppSkilldependency-cve-sweep
Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.
Also in 12 projects that use this
berntpoppSkillfleet-standard-adoption
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.
Also in 12 projects that use this
xfstudioSkilllinkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
Also in 6 projects that use this
xfstudioSkillteam-composition-analysis
This skill should be used when the user asks to "plan team
Also in 5 projects that use this
HABUBUSSSkillproject-guidelines-example
Also in 16 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 13 projects that use this
- +2 more from berntpopp
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- affaan-m/ECC★ 246ksame name
- github/awesome-copilot★ 41ksame name
- langfuse/langfuse★ 37ksame name
- nearai/ironclaw★ 13ksame name
- joe-bell/cva★ 6.9ksame name
- doorkeeper-gem/doorkeeper★ 5.5ksame name
- github/squad★ 3.4ksame name
- compozy/compozy★ 2.9ksame name
- trycompai/comp★ 2.1ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
181 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- atomic-commitSkill
- mcp-tool-extensionSkill
- mutation-lifecycleSkill
- odoo-compatSkill
- releaseSkill
- web-uiSkill
- atomic-commitSkill
- mcp-tool-extensionSkill
- mutation-lifecycleSkill
- odoo-compatSkill
- releaseSkill
- security-reviewSkill
- web-uiSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 163 edited versions we read keep these.
7
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 16
Never log, serialize, return, or put credentials in errors, audit details, metrics, or UI responses.
- Distinctive: line 20
Check tests still assert that canary values never appear in responses.
- Very specific: line 24
Keep policy default-deny when permissions is enabled.
- Distinctive: line 30
Do not add allow rules, legacy-mode shortcuts, or test-only bypasses to make a test pass.
- Distinctive: line 48
Never retry a mutation automatically.
- Very specific: line 56
Keep authentication on every admin /api route.
- Very specific: line 59
Do not disable TLS or HTTPS warnings, and keep ODOO_MCP_UI_BIND local-only by default.
- Distinctive: line 61
Keep response-size limits and timeouts enforced.
- Distinctive: line 65
Add regression tests for every security boundary changed.
- Distinctive: line 66
Run the full quality gate from AGENTS.md.
“Common” is measured: kept by at least 6 in 10 of the 163 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 Review
AGENTS.md is the canonical rule set. Run this review before committing any
change that touches a trust boundary.
1. Secrets and credentials
SecretStringmust keep redactedDebugandSerialize.- Environment-backed credentials stay in
password_env; resolved values are never written back toconfig.json. - Never log, serialize, return, or put credentials in errors, audit details, metrics, or UI responses.
redacted_config_valuemust keep returning an emptypasswordandhas_passwordinstead of the secret.- Check tests still assert that canary values never appear in responses.
2. Authorization
- Keep policy default-deny when
permissionsis enabled. - Preserve precedence: field and method, operation, model, instance, then global.
- Deny must win over allow in the same scope.
requires_model,requires_client, capability mapping, and operation identity must match the tool being executed.- Do not add allow rules, legacy-mode shortcuts, or test-only bypasses to make a test pass.
- Reject unknown or conflicting policy input before saving it.
3. Input and query protection
- Domains are parsed as nested clauses with allowed operators and prefix logical operators; no raw Odoo domain strings.
- Enforce
max_domain_depth,max_domain_terms,max_domain_in_values,max_requested_fields,max_read_ids,max_query_limit, andmax_response_records. - Validate
orderclauses; reject injection and unsupported tokens. - Reject malformed input before it reaches Odoo.
4. Mutations and audit
- Mutations still require preview, risk classification, approval when needed, idempotency, single execution, verification, and audit.
- Never retry a mutation automatically.
- Audit details are redacted and truncated; hash-chain verification must keep working.
- Approval and idempotency state transitions must remain guarded.
5. Session and transport
- UI sessions use HttpOnly, SameSite=Strict cookies.
- Keep authentication on every admin
/apiroute; only/, static assets,/health,/ready,/api/version,/api/login, and/api/logoutstay public. - Do not disable TLS or HTTPS warnings, and keep
ODOO_MCP_UI_BINDlocal-only by default. - Keep response-size limits and timeouts enforced.
6. Tests and review
- Add regression tests for every security boundary changed.
- Run the full quality gate from
AGENTS.md. - Review the staged diff specifically for secrets, debug output, and weakened defaults before committing.
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.

