dhpk-project-conventions

dhpk-project-conventions is a cursor rule for Cursor from hmj1026/dhpk. It costs 11 tokens per session (1,233 once invoked), scanned A, original, MIT.

A set of rules for contributing to the dhpk repository, including its branch model, pull-request target, and limits on Git actions. It applies only to that repository, not to consumer projects.

In plain words
What is it for?
Use it when developing dhpk and deciding where branches and pull requests should go or whether staging, committing, pushing, and stashing are authorized.
Why use it?
It prevents repository-specific contribution rules from being mistaken for general instructions and helps keep branch and pull-request changes within the intended workflow.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions AGENTS.md; $skill-name invocation.

Good fit Use it when developing dhpk and deciding where branches and pull requests should go or whether staging, committing, pushing, and stashing are authorized.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/hmj1026/dhpk/dhpk-project-conventions
View source ↗ hmj1026/dhpk
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/hmj1026/dhpk

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 dhpk-project-conventions

README.md
[![agentmods](https://agentmods.dev/badge/rules/hmj1026/dhpk/dhpk-project-conventions/github.svg)](https://agentmods.dev/rules/hmj1026/dhpk/dhpk-project-conventions)
Your own site
<a href="https://agentmods.dev/rules/hmj1026/dhpk/dhpk-project-conventions"><img src="https://agentmods.dev/badge/rules/hmj1026/dhpk/dhpk-project-conventions/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 dhpk-project-conventions

Your own site · 80×15
<a href="https://agentmods.dev/rules/hmj1026/dhpk/dhpk-project-conventions"><img src="https://agentmods.dev/badge/rules/hmj1026/dhpk/dhpk-project-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,233 The whole file, excluding the scripts and references it only reads on demand.
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.00011 $0.01233
Opus 5.5 $0.00004 $0.00493
Sonnet 5.5 $0.00002 $0.00247
Haiku 4.5 $0.00001 $0.00123

Measured yesterday against content hash 183959b108c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dhpk-project-conventions 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.

cursor/rules/dhpk-project-conventions.mdc · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

dhpk Project Convention

Applies only when developing the dhpk repository. Consumer projects supply their own Project Convention; portable skills and execution bundles do not load this file. Its presence among Claude package-root maintainer documents does not make it a consumer workflow requirement.

The root AGENTS.md selects this convention alongside the generic execution policy. User authorization and the execution-policy kernel's safety, dirty-work, and evidence boundaries still apply.

Branches and Git authority

Use dhpk's git-flow model: feat|fix|docs|refactor/* targets develop; release work integrates into the configured release branch. This repository's PR base is develop. For create-pr, pass --base develop or supply {TARGET_BRANCH} as develop through the project instructions.

Keep staging, commit, push, and stash inside the user's authorization and assigned scope. Use the applicable commit and PR tools or sufficient existing evidence; a verification verdict alone does not grant Git write authority. Before a follow-up push, check the PR's state and base so a merged/deleted branch does not receive orphaned work.

Hand PR merge to a human by default. When the user explicitly authorizes an agent to merge, open a ready pull request and use the maintainer delivery gate after its required checks pass. The live develop ruleset must require Validate harness assets. The gate merges with gh pr merge --merge for that exact head. It does not use --auto, --admin, or remote branch deletion. A classifier block on the merge command hands the PR URL to a human.

After syncing this checkout, check a locally installed compatibility projection when .agents/skills/.dhpk-projection.json exists with npm run check:local-skills. Use npm run sync:local-skills to update owned files from canonical sources and validate the result. Preserve reported modified or unmanaged conflicts; keep a backup before repair. This local installation check is separate from package CI and is not required in a fresh checkout without that receipt.

Read the full file on GitHub · 101 lines

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. yesterday Changed · +1 lines · +7 tokens per session 183959b108c9
  2. 3d ago Changed · +14 lines cdc58f9459d1
  3. 6d ago Changed · +7 lines 8ab67407f173
  4. 11d ago First seen · 79 lines · 4 tokens per session scan A 6a9a6cd8686f

Subscribe to this mod's changes

dhpk-project-conventions is a cursor rule published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 1,233 once invoked, about $0.0000 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-10-23.