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 Guild-Agents/guild --skill create-prgit clone --depth 1 https://github.com/Guild-Agents/guildWrote 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/guild-agents/guild/create-pr)<a href="https://agentmods.dev/skills/guild-agents/guild/create-pr"><img src="https://agentmods.dev/badge/skills/guild-agents/guild/create-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/guild-agents/guild/create-pr"><img src="https://agentmods.dev/badge/skills/guild-agents/guild/create-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.00014 | $0.01075 |
| Opus 5.5 | $0.00006 | $0.00430 |
| Sonnet 5.5 | $0.00003 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade A, and why
create-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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Creates a pull request from the current feature branch with a structured summary, test results, and change description. Closes the pipeline loop: init -> build-feature -> create-pr.
When to use
- After completing a feature with
/build-feature - When you have changes on a feature branch ready for review
- To create a well-structured PR without manual formatting
Usage
/create-pr
Process
Step 1 -- Verify branch state
- Confirm you are NOT on
mainordevelop-- refuse to create PR from default branches - Run
git statusto check for uncommitted changes -- if any, warn the user and ask whether to commit first - Run
git log main..HEAD --onelineto get the list of commits that will be in the PR - If there are no commits ahead of main, report that there is nothing to PR
Step 2 -- Gather context
Collect the information needed for the PR description:
- Commits:
git log main..HEAD --oneline-- list of all commits on this branch - Diff summary:
git diff main..HEAD --stat-- files changed with line counts - Test results: Run project tests (e.g.,
npm test) and capture pass/fail - Lint results: Run project lint (e.g.,
npm run lint) and capture pass/fail - Branch name: Extract feature name from the branch (e.g.,
feature/dark-mode->dark-mode)
If tests or lint fail, warn the user but allow them to proceed (some PRs are draft/WIP).
Step 3 -- Generate PR description
Build a structured PR description:
## Summary
[2-4 bullet points describing what this PR does, derived from commit messages]
## Changes
[File-level summary from git diff --stat]
## Test plan
- [x] Tests: [pass/fail] ([count] tests)
- [x] Lint: [pass/fail]
- [ ] [Any manual verification steps if applicable]
Step 4 -- Create the PR
- Push the branch to origin:
git push -u origin [branch-name] - Create the PR using
gh pr create:- Title: derived from branch name or first commit message (max 70 chars)
- Body: the generated description from Step 3
- Base:
main(or the project's default branch)
- Report the PR URL to the user
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 · 130 lines · 14 tokens per session scan A 19e00e506153
create-pr is a skill published in the GitHub repository Guild-Agents/guild (4 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,075 once invoked, about $0.0001 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
setup-caliber
Sets up Caliber for automatic AI agent context sync. Installs pre-commit hooks so CLAUDE.md, Cursor rules, and Copilot instructions update automatically on every commit. Use when Caliber hooks are not yet installed or when the user asks about keeping agent configs in sync.
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
worktree-isolate
A workflow for doing risky or experimental changes in an isolated Git worktree, which is a separate working copy of the same repository. The changes can then be merged into the main checkout or discarded.
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
git-town
This skill should be used when the user asks to "create a feature branch", "start a new feature", "sync my branch", "sync with main", "update from main", "create a PR", "create a pull request", "ship a feature", "merge and clean up", "handle merge conflicts", "resolve conflicts in git-town", "create stacked branches"…