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.
git clone --depth 1 https://github.com/hmj1026/dhpkWrote 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.
[](https://agentmods.dev/rules/hmj1026/dhpk/execution-policy-kernel)<a href="https://agentmods.dev/rules/hmj1026/dhpk/execution-policy-kernel"><img src="https://agentmods.dev/badge/rules/hmj1026/dhpk/execution-policy-kernel/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.
<a href="https://agentmods.dev/rules/hmj1026/dhpk/execution-policy-kernel"><img src="https://agentmods.dev/badge/rules/hmj1026/dhpk/execution-policy-kernel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00871 | $0.00871 |
| Opus 5.5 | $0.00348 | $0.00348 |
| Sonnet 5.5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
execution-policy-kernel 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Policy Kernel
This is the short, always-visible safety kernel. Read it before loading a
conditional stack, version, review, or OpenSpec reference. The full policy in
${POLICY_BUNDLE_ROOT}/rules/execution-policy.md remains the single source of
truth for routing precedence, dispatch selection, and reviewer closure; this
file does not duplicate its tables. The caller selects one policy file first;
the selected file has the shape <bundle-root>/rules/execution-policy.md, and
POLICY_BUNDLE_ROOT is the real parent of that file's containing rules
directory.
Safety and authorization
- Work only in the user-authorized repository, files, and task scope. A new external side effect, provider, message, or materially different target needs explicit authorization.
- Preserve existing dirty worktree changes. Do not reset, checkout, stash, delete, overwrite, or auto-commit user work; report ownership ambiguity before editing an overlapping path.
- Treat secrets, credentials, tokens, private account identifiers, and raw user data as redacted evidence. Do not paste them into logs, prompts, or generated artifacts.
Invocation and route boundary
The selected entry Skill's local command boundary parses flags once through its
immutable route parser. Downstream policy consumes that route result and must
not reconstruct precedence from the cleaned query. The target invocation class
still applies: an explicit-only target is presented with its exact command
form rather than called through a delegated Skill handoff.
Completion boundary
Do not claim completion from intent, a successful dispatch call, or a source scan alone. Completion requires the requested scope, actual verification evidence, and an explicit record of skipped, unavailable, blocked, or environment-dependent checks. A pending reviewer, unresolved gate, or unverified runtime premise remains open.
Evidence snapshots
Verification and review evidence is valid only for the snapshot and scope it
examined. Run mutating steps, including precommit's lint:fix and build,
before final affected verification or review. A later mutation invalidates
evidence for the scope it touches; recheck that scope before claiming completion.
Evidence outside the mutated scope remains reusable when its source,
acceptance criteria, configuration, tools, and environment still apply; do not
rerun it by default.
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.
- yesterday Changed · +868 tokens per session 691bec02e898
- 6d ago Changed · +10 lines 2ceaf3cb6245
- 28d ago Changed · +3 lines 162dee0b8677
- 1mo ago Changed · +4 lines e69f9cdd69ab
- 1mo ago Changed 993e2db337dd
- 1mo ago First seen · 69 lines · 3 tokens per session scan A 0e96a19cdbc5
execution-policy-kernel is a cursor rule published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 871 tokens to every session, about $0.0035 per session on Opus 5.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-09-05.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.