Security Audit
TheDecipherist/claude-code-mastery
Checks a codebase for hardcoded secrets, vulnerable dependencies, weak input handling, weak authentication and unsafe transport settings before deployment or merge.
A skill your agent uses when reviewing HTTP response headers for defense-in-depth security hardening on any web application.
Install Permissions Policy
$ npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist permissions-policy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/permissions-policy .claude/skills/permissions-policy && rm -rf skills-srcUse ~/.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/
Install the "permissions-policy" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/permissions-policy into .claude/skills/permissions-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "permissions-policy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/permissions-policyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist permissions-policy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/permissions-policy .agents/skills/permissions-policy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "permissions-policy" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/permissions-policy into .agents/skills/permissions-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "permissions-policy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist permissions-policy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/permissions-policy .cursor/skills/permissions-policy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "permissions-policy" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/permissions-policy into .cursor/skills/permissions-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "permissions-policy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/permissions-policy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist permissions-policy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/permissions-policy .gemini/skills/permissions-policy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "permissions-policy" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/permissions-policy into .gemini/skills/permissions-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "permissions-policy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist permissions-policyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/permissions-policy .github/skills/permissions-policy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "permissions-policy" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/permissions-policy into .github/skills/permissions-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "permissions-policy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist permissions-policy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/permissions-policy .opencode/skills/permissions-policy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "permissions-policy" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/permissions-policy into .opencode/skills/permissions-policy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "permissions-policy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
permissions-policy- GitHub stars
- 74k
- Token cost
- ~565 tokens
- SKILL.md length
- 241 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing HTTP response headers for defense-in-depth security hardening on any web application.
- Reviewing HTTP response headers for defense-in-depth security hardening on any web application
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Security review
What it does
Permissions Policy is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing HTTP response headers for defense-in-depth security hardening on any web application.
Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Security, covering Security review and Secure coding. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Reviewing HTTP response headers for defense-in-depth security hardening on any web application
- Tasks that involve Security review
- Tasks that involve Secure coding
Example prompts
- “/permissions-policy”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. 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
Links to these hosts (documentation or services it may open):
frontendchecklist.io
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
Permissions Policy loads about 565 tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 31 tokens; SKILL.md has 241 words of instructions outside code blocks.
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 thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 241 words, ~565 tokens.
Download SKILL.mdSave it as
.claude/skills/permissions-policy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- permissions-policy
- description
- Use when reviewing HTTP response headers for defense-in-depth security hardening on any web application.
- metadata.category
- security
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 15
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/security/permissions-policy
Set a Permissions-Policy header
A site compromised by XSS that has unrestricted camera and microphone access can silently record the user. Permissions-Policy limits which browser APIs are available, reducing attacker capabilities even after a successful injection.
Quick Reference
- Use
Permissions-Policyto disable browser features your site does not use (camera, microphone, geolocation, payment) - Syntax:
Permissions-Policy: camera=(), microphone=(), geolocation=()— empty()means denied to all - Previously called
Feature-Policy— the old syntax is deprecated and only supported in older browsers - Restricting unused features limits the blast radius if your site is compromised by XSS
- Third-party iframes inherit page restrictions unless you explicitly grant them permissions
Check
Check whether the server sends a Permissions-Policy header and review which browser features are allowed or denied. Identify any powerful features (camera, microphone, geolocation, payment, USB) that are enabled but not required by the application.
Fix
Add a Permissions-Policy header that disables all browser features your site does not use. Start with camera=(), microphone=(), geolocation=() and expand the list based on what the application actually needs.
Explain
Explain what the Permissions-Policy header does, how it restricts browser APIs like camera and geolocation, and why disabling unused features improves security.
Code Review
Review server config, headers, forms, and integration points related to Set a Permissions-Policy header. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/security/permissions-policy
© thedaviddias, MIT. 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 1 other file (references) in skills/permissions-policy of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Permissions Policy 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Permissions Policy this skillthedaviddias/Front-End-Checklist | 74k | — | ~565 | Automated safety check: Pass | MIT | |
| Security AuditTheDecipherist/claude-code-mastery | 551 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Humble Header Report Analystrfc-st/humble | 379 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Pre-Commit Security Scanzereight/gitlab-mcp | 2k | 1 repos | ~859 | Automated safety check: Notes | MIT | |
| Codewhale Security Reviewcodewhale-hq/Codewhale | 41k | — | ~844 | Automated safety check: Pass | MIT | |
| Security Hardeningancoleman/ai-design-components | 525 | — | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
Humble Header Report Analyst
rfc-st/humble
Parses reports from the humble HTTP security header analyzer and explains each finding with remediation steps for DevOps teams.
Pre-Commit Security Scan
zereight/gitlab-mcp
Runs a fast security sweep of recent code changes before a commit or PR, checking for leaked secrets, vulnerable dependencies, unsafe input handling and auth gaps.
Codewhale Security Review
codewhale-hq/Codewhale
Reviews a diff, module or network surface for exploitable defects, mapping trust boundaries and sinks, then reports only findings with a verified reachable path and a fix.
Security Hardening
ancoleman/ai-design-components
Reduces attack surface across OS, container, cloud, network, and database layers using CIS Benchmarks and zero-trust principles.
Security Nextjs
IgorWarzocha/Opencode-Workflows
Review Next.js security audit patterns for App Router and Server Actions.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Permissions Policy
What does Permissions Policy do?
A skill your agent uses when reviewing HTTP response headers for defense-in-depth security hardening on any web application. Permissions Policy is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing HTTP response headers for defense-in-depth security hardening on any web application.
When should I use Permissions Policy?
Permissions Policy fits situations like: reviewing HTTP response headers for defense-in-depth security hardening on any web application; tasks that involve Security review; tasks that involve Secure coding.
How do I install Permissions Policy in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a claude-code`. Or copy the skill folder (skills/permissions-policy in thedaviddias/Front-End-Checklist) into .claude/skills/permissions-policy in your project. Claude Code loads it when a task matches its description.
How do I install Permissions Policy in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill permissions-policy -a codex`. Or copy the skill folder (skills/permissions-policy in thedaviddias/Front-End-Checklist) into .agents/skills/permissions-policy in your project. Codex loads it when a task matches its description.
Can I use Permissions Policy 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 thedaviddias/Front-End-Checklist --skill permissions-policy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/permissions-policy, .gemini/skills/permissions-policy, .github/skills/permissions-policy and .opencode/skills/permissions-policy in your project.
What does Permissions Policy need to run?
SKILL.md names no scripts, command-line tools or credentials: Permissions Policy is instructions for the agent only.
Does Permissions Policy access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Permissions Policy 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 Permissions Policy use?
Permissions Policy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Permissions Policy use?
About 565 tokens (SKILL.md is roughly 2.3k 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 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Permissions Policy?
Skills that share tags, products or a category with Permissions Policy: Security Audit (TheDecipherist/claude-code-mastery, 551 stars), Humble Header Report Analyst (rfc-st/humble, 379 stars), Pre-Commit Security Scan (zereight/gitlab-mcp, 2k stars) and Codewhale Security Review (codewhale-hq/Codewhale, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Permissions Policy?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.