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 skills add hmj1026/dhpk --skill dhpk-project-auditgit 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/skills/hmj1026/dhpk/dhpk-project-audit)<a href="https://agentmods.dev/skills/hmj1026/dhpk/dhpk-project-audit"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-project-audit/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/skills/hmj1026/dhpk/dhpk-project-audit"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-project-audit.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.00064 | $0.00805 |
| Opus 5.5 | $0.00026 | $0.00322 |
| Sonnet 5.5 | $0.00013 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
dhpk-project-audit 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.
This is a copy
89% identical to project-audit — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Audit
$SKILL_DIR denotes the physical directory containing the selected SKILL.md;
it is path notation, not an ambient environment variable or repository-root
lookup. Resolve it before running the audit from an arbitrary consumer cwd.
When NOT to Use
- Security-specific review (use
/dhpk:change-verdict --mode security) - Runtime performance profiling
- Mid-development review (use
/dhpk:change-verdict --mode code)
Procedure
- Run
node "$SKILL_DIR/scripts/audit.js" --jsonto collect deterministic scores - Parse the JSON output — overall_score, status, dimensions, checks, findings, next_actions
- If status = Blocked (P0 findings) — highlight critical gaps, suggest immediate fixes
- If status = Needs Work (P1 findings) — format improvement roadmap by dimension
- If status = Healthy — summarize strengths, note any P2 improvements
- Add qualitative interpretation beyond the scores (e.g., "test ratio is good but concentrated in unit tests")
Script Integration
The audit script runs 12 deterministic checks across 5 dimensions:
| Dimension | Checks | What It Measures |
|---|---|---|
| oss | 2 | LICENSE, README quality |
| robustness | 3 | CI config, lint/typecheck, test ratio |
| scope | 2 | Declared features vs implementation, AC completion |
| runnability | 3 | Package manifest, scripts, env/Docker setup |
| stability | 2 | Lock file + audit, type configuration |
Scoring Model
- Each check:
1(pass) /0.5(partial) /0(fail) /N/A(skipped) - Dimension score:
applicable_sum / applicable_count * 100 - Overall score: average of dimension scores
- Confidence:
applicable_checks / total_checksper dimension
Status Determination
| Status | Condition | Exit Code |
|---|---|---|
| Blocked | Any P0 finding | 2 |
| Needs Work | No P0, has P1 | 1 |
| Healthy | No P0/P1 | 0 |
Script Failure Fallback
If the script fails, report the error and suggest running manually:
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +1 lines 8eeb2289907b
- 23d ago Changed · +4 lines 0a8e07c8f5a7
- 1mo ago First seen · 95 lines · 64 tokens per session scan A 4badae0745a4
dhpk-project-audit is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 805 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to project-audit, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
defect
A command for registering a software defect, meaning behavior that does not work as intended, and creating a task to fix it. The defect and its fix task receive tracked IDs and are stored in the project's backlog and task folders.
propose-issue
Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…
workflow-audit-emit-issues
After a codebase audit, groups audit findings by subsystem (path prefix) and emits them as context-rich GitHub issues with template discovery, label selection, and a batch preview-confirm gate before filing. Keywords — audit findings grouped github issues subsystem emit.