manifest-and-permissions-rules

manifest-and-permissions-rules is a cursor rule for Cursor from paulpham157/paul-s-cursor-rules. It costs 58 tokens per session, scanned A, original, MIT.

A set of rules for an extension manifest, the file that declares an extension’s configuration and requested access. It recommends manifest version 3 and limiting permissions to what the extension needs.

In plain words
What is it for?
Use it when configuring extension metadata, choosing permissions, and deciding which access should be optional.
Why use it?
It helps prevent an extension from requesting unnecessary access and keeps its configuration aligned with current manifest guidance.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when configuring extension metadata, choosing permissions, and deciding which access should be optional.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/paulpham157/paul-s-cursor-rules/manifest-and-permissions-rules
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/paulpham157/paul-s-cursor-rules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for manifest-and-permissions-rules

README.md
[![agentmods](https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/manifest-and-permissions-rules/github.svg)](https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/manifest-and-permissions-rules)
Your own site
<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/manifest-and-permissions-rules"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/manifest-and-permissions-rules/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for manifest-and-permissions-rules

Your own site · 80×15
<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/manifest-and-permissions-rules"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/manifest-and-permissions-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 This file is loaded in full into every session.
When invoked 58 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.00058
Opus 5 $0.00029 $0.00029
Sonnet 5 $0.00012 $0.00012
Haiku 4.5 $0.00006 $0.00006

Measured 11d ago against content hash 9e41de3bc4bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

manifest-and-permissions-rules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

1/framework_rules/rules/chrome-extension-dev-js-typescript-cursorrules-pro/manifest-and-permissions-rules.mdc · 7 lines

What it actually says


description: Rules for configuring the extension manifest and handling permissions securely. globs: **/manifest.json

  • Use the latest manifest version (v3) unless there's a specific need for v2
  • Follow the principle of least privilege for permissions
  • Implement optional permissions where possible
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 7 lines · 58 tokens per session scan A 9e41de3bc4bf

Subscribe to this mod's changes

manifest-and-permissions-rules is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It adds 58 tokens to every session, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.