agentsclimarketplace

Security authorization

Skill planifest/planifest-framework/planifest-framework/external-skills/security-authorization

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill security-authorization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Security workflow for authorization boundaries, least-privilege policy, and enforcement design. Use when permission models, access decisions, or privileged action controls are required; do not use for authentication factor selection or non-security quality tuning.

SKILL.md

2.5 KB, 429 tokens by cl100k_base, as published. Nobody here has run it

Security Authorization

Overview

Use this skill to build authorization systems that enforce least privilege across APIs, UI actions, and background jobs.

Scope Boundaries

  • Role/permission models are being introduced or revised.
  • Resource-scoped access control must be consistent across services.
  • Privileged workflows require explicit separation-of-duty controls.

Templates And Assets

  • Authorization policy matrix:
    • assets/authorization-policy-matrix-template.md

Inputs To Gather

  • Actor categories, resources, and sensitive actions.
  • Data classification and tenant or domain boundaries.
  • Existing policy model and enforcement points (API gateway, service layer, DB layer).
  • Abuse scenarios (horizontal/vertical privilege escalation, confused deputy, missing object-level checks).

Deliverables

  • Authorization model (RBAC, ABAC, ReBAC, or hybrid) with policy decision rules.
  • Enforcement map (where decisions are made and where they are enforced).
  • Default-deny and exception policy with break-glass controls.
  • Verification plan for privilege escalation and cross-tenant isolation tests.

Workflow

  1. Enumerate subject-action-resource tuples and fill assets/authorization-policy-matrix-template.md.
  2. Select model based on change frequency, policy complexity, and auditability requirements.
  3. Define canonical policy evaluation order and conflict resolution rules.
  4. Ensure object-level authorization is checked server-side for every mutable/read-sensitive path.
  5. Specify admin and break-glass flows with time limits, approval, and audit logging.
  6. Validate policy propagation consistency across UI hints and backend enforcement.
  7. Run abuse-case tests for IDOR, privilege creep, and stale privilege revocation.

Quality Standard

  • Authorization decisions are default-deny and centrally explainable.
  • Every privileged operation has a single source of policy truth.
  • Policy updates are auditable and revocation latency is acceptable.
  • Cross-tenant and cross-domain boundaries are explicitly tested.

Failure Conditions

  • Stop when enforcement relies on client-side checks.
  • Stop when policy conflicts are unresolved or implicit.
  • Escalate when least-privilege requirements cannot be implemented without structural change.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.