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.
npx agentmods add rules/hmj1026/dhpk/execution-policy-kernelgit 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.svg" alt="Measured on agentmods" 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.00003 | $0.00682 |
| Opus 5 | $0.00002 | $0.00341 |
| Sonnet 5 | $0.00001 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
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 today.
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 — 69 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
execution-policy.md remains the single source of
truth for routing precedence, dispatch selection, and reviewer closure; this
file does not duplicate its tables.
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
Command entry points parse flags once through the immutable
skills/flow-drive/scripts/route-result.js boundary. 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.
OpenSpec planner gate
Before the first write wave of an existing OpenSpec apply, count the unchecked
tasks in the task artifact. If there are >=2 unchecked tasks (two or more), a
planner dispatch is mandatory before any writer starts. Record the planner's
actionable handoff with the dependency order, the exact owner and write scope
for each task, and the next checkpoint; an unrecorded or incomplete planner
handoff does not authorize a write wave. If exactly one clear task remains,
record planner=skipped and continue through the normal decision, writer, and
verification gates. This planner gate is a lifecycle invariant: it remains
active when orchestration_dispatch=off, which disables implementation
worker/reasoner routing but does not bypass mandatory pre-write planning or
verification.
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.
- today 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 3 tokens to every session and 682 once invoked, about $0.0000 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-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.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.