origin-permission-audit

Audit, classify, and revoke session-granted IAM roles and API scopes with verification.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/Aki2022/skills --skill origin-permission-audit-aki2022
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: origin-permission-audit
Source: https://github.com/Aki2022/skills/tree/main/origin-permission-audit
Command: npx skills add https://github.com/Aki2022/skills --skill origin-permission-audit-aki2022

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Elevated access granted during a work session often lingers after the task ends, creating unnecessary security exposure. This Skill audits permissions granted during the current or resumed session, revokes temporary grants, and verifies removal before the session closes. ## Core Features & Use Cases - Session Grant Discovery: Lists every IAM role, API scope, bucket binding, or equivalent elevated access granted during the session, with principal, resource, and reason. - Temporary vs Standing Classification: Distinguishes one-off investigation or debugging access from access required by documented recurring workstreams. - Verified Revocation: Revokes temporary grants with the narrowest available command, then re-queries the principal and resource to confirm removal. - Use Case: After a debugging session where you granted a service account temporary bucket read access, run this audit before closing the session to revoke the binding, verify it is gone, and produce a per-grant report. ## Quick Start Use origin-permission-audit to audit and revoke any elevated access granted during this session before closing it.

Frequently Asked Questions about origin-permission-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit IAM permissions granted during a session?

List every grant the session made with its principal, resource, exact role or scope, and reason. Classify each as temporary or standing, revoke temporary grants with the narrowest command, then re-query to verify removal.

How to safely revoke temporary IAM roles and API scopes?

Resolve the exact principal, resource, role, and scope first, then use the narrowest available revocation command rather than project-wide or wildcard removal. Always re-query afterward to confirm the grant is gone and the baseline remains.

Should read-only access granted for debugging be revoked?

Yes. One-off investigation, remediation, or debugging access is treated as temporary by default, including read-only access. Only access tied to a documented recurring workstream or automation is classified as standing.

What happens if permission revocation is blocked by an access boundary?

The audit returns the exact revocation command for a human to execute, waits for confirmation, and then verifies the removal. It never claims success from a removal command alone without verification.

When should I not run a session permission audit?

Do not use it to audit or revoke pre-existing access based on suspicion, since it only covers grants made by the current or a visibly resumed session. It also stops when the action falls outside the session's authorization envelope.