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/huangjia2019/claude-code-engineeringWrote 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/commands/huangjia2019/claude-code-engineering/pr-create)<a href="https://agentmods.dev/commands/huangjia2019/claude-code-engineering/pr-create"><img src="https://agentmods.dev/badge/commands/huangjia2019/claude-code-engineering/pr-create/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/commands/huangjia2019/claude-code-engineering/pr-create"><img src="https://agentmods.dev/badge/commands/huangjia2019/claude-code-engineering/pr-create.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.00000 | $0.00297 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
pr-create 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 60 lines · 0 tokens per session scan A 6c2ae368a08f
pr-create is a command published in the GitHub repository huangjia2019/claude-code-engineering (1,139 stars, last pushed 2mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 297 tokens. 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.
Other commands, from other repositories
dashboard-git-init
Initialise a git repo in a directory. Usage /dashboard:git-init [cwd].
dashboard-git-stash-pop
Use the pi-dashboard skill (see ../SKILL.md). Discover the base URL: prefer the $PIDASHBOARDPORT or $DASHBOARDPORT env var, else read the port from /.pi/dashboard/config.json (default 8000); BASE="http://localhost:$PORT". When auth is enabled, include the JWT cookie. Resolve any via GET /api/sessions, matching the…
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.
dashboard-git-branches
List git branches for the current dir (current marked ). Runs locally, no LLM.
release
Command "release" from voodootikigod/skills-check, covering arguments and steps.
cr
Tool-driven implementation of unresolved PR/MR review comments on GitHub, GitLab or Bitbucket: fetch every comment thread plus the out-of-thread notices (review bodies, bot summaries), evaluate each for technical validity, implement valid ones one at a time with a full validation pass after each, and scan the codebase…