Rego is the declarative policy language used by Open Policy Agent (OPA). This tile covers writing and testing Rego policies for Kubernetes admission control, Terraform and infrastructure-as-code plan validation, Docker container authorization, HTTP API authorization, RBAC and role-based access control, data filtering, metadata annotations with opa inspect, and OPA policy testing with opa test.
99
Quality
Pending
Does it follow best practices?
Impact
99%
1.19xAverage score across 31 eval scenarios
Pending
The risk profile of this skill
{
"context": "Evaluates whether the agent applies the two cross-cutting Terraform IaC patterns that appear in every policy: using import rego.v1 (not import future.keywords) and normalizing input with tfplan := object.get(input, \"plan\", input) so the policy works with both raw Terraform and HCP Terraform/Enterprise input structures. These criteria are tested here and excluded from all other terraform IaC scenarios to avoid inflating their scores.",
"type": "weighted_checklist",
"checklist": [
{
"name": "import rego.v1",
"description": "The policy uses `import rego.v1` (not `import future.keywords` or no import at all)",
"max_score": 37
},
{
"name": "object.get input normalization",
"description": "The policy defines `tfplan := object.get(input, \"plan\", input)` as a package-level rule and uses `tfplan.resource_changes` throughout — never `input.resource_changes` directly. This ensures the policy works with both raw Terraform and HCP Terraform/Enterprise input structures.",
"max_score": 38
},
{
"name": "Tests pass",
"description": "All tests pass when running `opa test . -v`",
"max_score": 25
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31