Agent skill

Audit Access Policy Enforcement

by cyberful in cyberful/cyberful

Audit where access policy is decided and enforced across source, configuration, services, caches, jobs, and data stores, including deny behavior and decision-input integrity.

AGPL-3.0Auto-check passedSecurity

Install Audit Access Policy Enforcement

skills CLI
$ npx skills add cyberful/cyberful --skill audit-access-policy-enforcement -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cyberful/cyberful audit-access-policy-enforcement --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/audit-access-policy-enforcement .claude/skills/audit-access-policy-enforcement && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
audit-access-policy-enforcement
GitHub stars
135
Token cost
~725 tokens
SKILL.md length
269 words
Files
4 (incl. references, assets)
Skills in repo
85
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Audit where access policy is decided and enforced across source, configuration, services, caches, jobs, and data stores, including deny behavior and decision-input integrity.

  • Security work in your project
  • SKILL.md covers Build the decision ledger, Trace enforcement, Evaluate policy integrity and Report evidence
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Audit Access Policy Enforcement is an agent skill from cyberful/cyberful. Audit where access policy is decided and enforced across source, configuration, services, caches, jobs, and data stores, including deny behavior and decision-input integrity.

Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `agents/openai.yaml` and `references/policy-enforcement-review.md`).

It sits in Security. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.

When your agent uses it

  • Security work in your project

Example prompts

  • “/audit-access-policy-enforcement”

What it can do on your machine

Read from SKILL.md and the folder at commit ec598a6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Audit Access Policy Enforcement loads about 725 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 269 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~725
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 269 words, ~725 tokens.

Download SKILL.mdSave it as .claude/skills/audit-access-policy-enforcement/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
audit-access-policy-enforcement
description
Audit where access policy is decided and enforced across source, configuration, services, caches, jobs, and data stores, including deny behavior and decision-input integrity.
metadata.domain
identity-security
metadata.subdomain
access-policy
metadata.triggers
access policy audit, authorization enforcement review, policy decision point, policy enforcement point, default deny analysis, entitlement evaluation
metadata.tags
authorization, policy-engine, access-control, default-deny, entitlement, code-audit

Audit Access Policy Enforcement

Trace a protected operation from entry point through decision inputs, policy evaluation, enforcement, resource access, side effects, and audit evidence. Use this skill for source and configuration review; use test-authorization-boundaries to exercise a scoped live matrix.

Build the decision ledger

Copy assets/policy-decision-ledger.csv. Record the actor, subject, tenant, resource, relationship, action, state, assurance, environment, policy source, decision point, enforcement point, cache, and durable effect for every material operation.

Read references/policy-enforcement-review.md before auditing a shared policy engine, delegated administration, or asynchronous path.

Trace enforcement

Start from routes, resolvers, handlers, consumers, scheduled jobs, and administrative entry points. Follow normalization and identity context into policy calls, then continue beyond the allow result to repository, storage, queue, notification, export, or external-service effects.

Compare sibling operations and alternate transports. Check middleware exclusions, direct repository use, bulk and relationship endpoints, cache keys, default and error branches, stale entitlements, impersonation, service credentials, and replayed jobs. Prove whether a missing, malformed, stale, or contradictory decision input fails closed.

Evaluate policy integrity

Determine who can author, approve, deploy, override, and observe policy. Check rule precedence, deny overrides, version pinning, rollback, test coverage, data dependencies, and whether policy changes invalidate cached decisions and long-lived work.

Report evidence

For each gap state the entry point, decision tuple, expected rule, actual code or configuration path, resource effect, alternate paths sharing the weakness, and the evidence needed for confirmation. Do not label dead code, a missing UI check, or a theoretical policy ambiguity as exploitable without a reachable server-side effect.

Code Audit remains read-only and offline. Do not alter policies, entitlements, identities, or production configuration while validating source conclusions.

© cyberful, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references, assets) in cyberful/builtin/skills/audit-access-policy-enforcement of cyberful/cyberful.

  • SKILL.md
  • agents/openai.yaml
  • assets/policy-decision-ledger.csv
  • references/policy-enforcement-review.md

Open the folder on GitHubat commit ec598a6

Compare with similar skills

Audit Access Policy Enforcement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Audit Access Policy Enforcement compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Access Policy Enforcement this skillcyberful/cyberful135—~725Automated safety check: PassAGPL-3.0
Deepsec Documentation Guidevercel-labs/deepsec8.1k—~956Automated safety check: PassApache-2.0
Skill Scannergetsentry/skills1k4 repos~2.5kAutomated safety check: WarnApache-2.0
Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit4811 repos~3.3kAutomated safety check: PassNone
Security Alert Triageelastic/agent-skills5921 repos~3.5kAutomated safety check: NotesApache-2.0
Shiro Attack CLISummerSec/ShiroAttack22.6k—~945Automated safety check: PassMIT

Similar skills

  • Deepsec Documentation Guide

    vercel-labs/deepsec

    Official

    Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.

    8.1k GitHub stars~956 tokensUpdated 12 days ago
    SecurityAuto-check passed
  • Skill Scanner

    getsentry/skills

    Official

    Scan agent skills for security issues. An agent skill from getsentry/skills.

    1k GitHub starsUsed in 4 repos~2.5k tokens
    SecurityAuto-check: warnings
  • Serenity Aleabitoreddit

    yan-labs/serenity-aleabitoreddit

    Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.

    481 GitHub starsUsed in 1 repo~3.3k tokens
    SecurityAuto-check passed
  • Security Alert Triage

    elastic/agent-skills

    Official

    Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.

    592 GitHub starsUsed in 1 repo~3.5k tokens
    SecurityAuto-check: notes
  • Shiro Attack CLI

    SummerSec/ShiroAttack2

    当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…

    2.6k GitHub stars~945 tokensUpdated 4 mo ago
    SecurityAuto-check passed
  • Cve Remediation

    rundeck/rundeck

    Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.

    6.3k GitHub stars~2.9k tokensUpdated yesterday
    SecurityAuto-check passed

More from cyberful/cyberful

All 85 skills in this repo
  • Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.

    135 GitHub stars~649 tokensUpdated 1 mo ago
    Auto-check passed
  • Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.

    135 GitHub stars~610 tokensUpdated 1 mo ago
    Auto-check passed
  • Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.

    135 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Content Discovery

    cyberful/cyberful

    Design and interpret advanced content discovery with ffuf and complementary web fuzzers.

    135 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Network Recon

    cyberful/cyberful

    Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.

    135 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Operate Sast Toolchain

    cyberful/cyberful

    Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.

    135 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Audit Access Policy Enforcement

What does Audit Access Policy Enforcement do?

Audit where access policy is decided and enforced across source, configuration, services, caches, jobs, and data stores, including deny behavior and decision-input integrity. Audit Access Policy Enforcement is an agent skill from cyberful/cyberful. Audit where access policy is decided and enforced across source, configuration, services, caches, jobs, and data stores, including deny behavior and decision-input integrity.

When should I use Audit Access Policy Enforcement?

Audit Access Policy Enforcement fits situations like: security work in your project.

How do I install Audit Access Policy Enforcement in Claude Code?

Run `npx skills add cyberful/cyberful --skill audit-access-policy-enforcement -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/audit-access-policy-enforcement in cyberful/cyberful) into .claude/skills/audit-access-policy-enforcement in your project. Claude Code loads it when a task matches its description.

How do I install Audit Access Policy Enforcement in Codex?

Run `npx skills add cyberful/cyberful --skill audit-access-policy-enforcement -a codex`. Or copy the skill folder (cyberful/builtin/skills/audit-access-policy-enforcement in cyberful/cyberful) into .agents/skills/audit-access-policy-enforcement in your project. Codex loads it when a task matches its description.

Can I use Audit Access Policy Enforcement in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cyberful/cyberful --skill audit-access-policy-enforcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-access-policy-enforcement, .gemini/skills/audit-access-policy-enforcement, .github/skills/audit-access-policy-enforcement and .opencode/skills/audit-access-policy-enforcement in your project.

What does Audit Access Policy Enforcement need to run?

SKILL.md names no scripts, command-line tools or credentials: Audit Access Policy Enforcement is instructions for the agent only.

Does Audit Access Policy Enforcement access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Audit Access Policy Enforcement safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Audit Access Policy Enforcement use?

Audit Access Policy Enforcement is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Access Policy Enforcement use?

About 725 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 515 tokens, read only when the agent opens those files.

What are the alternatives to Audit Access Policy Enforcement?

Skills that share tags, products or a category with Audit Access Policy Enforcement: Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars), Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 481 stars) and Security Alert Triage (elastic/agent-skills, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Access Policy Enforcement?

cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.

Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.