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 agentmods add skills/guild-agents/guild/create-prnpx skills add Guild-Agents/guild --skill create-prgit clone --depth 1 https://github.com/Guild-Agents/guildWhat 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 | $0.00014 | $0.01075 |
| Opus 5 | $0.00007 | $0.00537 |
| Sonnet 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 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.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,075 once invoked, about $0.0001 per session on Opus 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
codebase-memory
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions…
using-pi-subagents
Operate pi-subagents jobs safely, including direct-work decisions, least-privilege tool selection, thinking-level selection, delegation, bidirectional messaging, parallel starts, timeout selection, waiting, cancellation, result handling, verification, and writer isolation.
herdr
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires…
laravel-actions
Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions. Use when implementing reusable action classes (object/controller/job/listener/command), converting service classes/controllers/jobs into actions, orchestrating workflows via faked actions, or debugging action entrypoints and wiring.
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
Shade dropdown surface contract
DropdownMenu, Select, and Popover share one visual recipe (bg-surface-elevated-2 + border-border/60 dark:border-border/30 + shadow-md). Change them together. Trigger when editing any of those three Shade files.