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 dkmqflx/git-workflow-plugin --skill open-prgit clone --depth 1 https://github.com/dkmqflx/git-workflow-pluginWrote 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/dkmqflx/git-workflow-plugin/open-pr)<a href="https://agentmods.dev/skills/dkmqflx/git-workflow-plugin/open-pr"><img src="https://agentmods.dev/badge/skills/dkmqflx/git-workflow-plugin/open-pr/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/dkmqflx/git-workflow-plugin/open-pr"><img src="https://agentmods.dev/badge/skills/dkmqflx/git-workflow-plugin/open-pr.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.00126 | $0.00924 |
| Opus 5.5 | $0.00050 | $0.00370 |
| Sonnet 5.5 | $0.00025 | $0.00185 |
| Haiku 4.5 | $0.00013 | $0.00092 |
Grade A, and why
open-pr 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open PR
Push the current branch and open a pull request via gh pr create.
Run this after committing your changes (see commit-each). Once the PR is merged, clean up with branch-done or worktree-done.
When to apply
Opening a new PR for the current branch. Do not apply to update, review, or comment on an existing PR.
Steps
- Determine the base branch:
- If a
devbranch exists locally or on the remote (git show-ref --verify --quiet refs/heads/devorrefs/remotes/origin/dev), the base is alwaysdev. Stop here — do not fall through, whateverorigin/HEADpoints at. - Otherwise try
git symbolic-ref refs/remotes/origin/HEADand strip therefs/remotes/origin/prefix. - If that fails, use the first of
main,masterthat exists locally (git show-ref --verify --quiet refs/heads/<name>). - If none exist, stop and ask the user which branch is the base.
- If a
- Record the current branch:
git rev-parse --abbrev-ref HEAD. If it equals the base branch, stop and notify the user — there's nothing to open a PR from. - Check for uncommitted changes (
git status --porcelain). If any exist, stop and tell the user to commit first. - Check whether a PR already exists for this branch:
gh pr view --json url 2>/dev/null. If one does, stop and report its URL instead of creating a duplicate. - Push the branch:
git push -u origin HEAD. - Gather context for the PR description:
git log <base branch>..HEAD --oneline git diff <base branch>...HEAD - Draft a title (under 70 characters) and a body with a
## Summary(1–3 bullets) and## Test plan(checklist) section, covering all commits on the branch — not just the latest. - Collect any URLs the user passed with the invocation (
/open-pr <link>, or a link written anywhere in the request). If there is at least one, append a## Relatedsection listing them as bullets at the end of the body. If there is none, leave the section out — never ask the user for a link. - Show the drafted title and body to the user and get confirmation before creating.
- Create the PR:
gh pr create --base <base branch> --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
- Report the returned PR URL.
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 · 56 lines · 126 tokens per session scan A 7a3f4e6c73a2
open-pr is a skill published in the GitHub repository dkmqflx/git-workflow-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 126 tokens to every session and 924 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
dsh-plugin-publisher
A release tool for DSH plugins, where DSH is the DeepSeek Harness used to load these add-ons. It validates an existing plugin package, publishes it through npm, Git, or a tarball, and checks that the harness can load it.
lov-skill-optimizer
Audit and optimize one or more existing Agent Skills from a canonical source path, then bump semver, update README/SKILL.md/skill.yaml/CHANGELOG.md, and verify installed copies and catalog synchronization. Checks frontmatter, trigger quality, CLI hygiene, naming, portability, version drift, dirty worktrees, shared…
lov-rename-project
A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.
lov-gh-access
Open a private GitHub repo to external clients or contractors without making it public. Accepts a mixed list of GitHub usernames and/or email addresses, resolves each to a GitHub account (falling back to an email invitation when the user has no discoverable account yet), and invites them as collaborators with a chosen…
lov-skill-publisher
Publish or submit a validated Skill. Default to the LovStudio official website, run lov-skill-pricing automatically, and use other channels only when explicitly named.