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/darkcofy/sqlprism/creating-branches-and-prsnpx skills add darkcofy/sqlprism --skill creating-branches-and-prsgit clone --depth 1 https://github.com/darkcofy/sqlprismWrote 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/darkcofy/sqlprism/creating-branches-and-prs)<a href="https://agentmods.dev/skills/darkcofy/sqlprism/creating-branches-and-prs"><img src="https://agentmods.dev/badge/skills/darkcofy/sqlprism/creating-branches-and-prs.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.00558 |
| Opus 5 | $0.00028 | $0.00279 |
| Sonnet 5 | $0.00011 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
creating-branches-and-prs 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 4d 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.
What it actually says
Creating Branches and PRs
Naming Convention
Both branches and PR titles use the same format:
<type>-<issue_number>-<short-description>
Rules
- Lowercase, hyphens only — no spaces, underscores, slashes, or camelCase
- Type prefix — matches the issue label
- Issue number — the GitHub issue this work addresses
- Short description — 2-4 words summarizing the change
Types
| Type | When | Maps to label |
|---|---|---|
feat |
New functionality | enhancement |
fix |
Bug fix | bug |
chore |
Maintenance, CI, deps, migrations | chore |
Examples
| Issue | Branch / PR title |
|---|---|
| #8 Add repo_type column | chore-8-repo-type-column |
| #9 dbt render_models | feat-9-dbt-render-models |
| #11 Indexer reindex_files | feat-11-indexer-reindex-files |
| #14 Tests for reindex | feat-14-reindex-on-save-tests |
Creating a Branch
git checkout main
git pull origin main
git checkout -b <type>-<issue_number>-<short-description>
Creating a PR
Link the PR to its issue using Closes #<number> in the body. This auto-closes the issue on merge.
gh pr create \
--title "<type>-<issue_number>-<short-description>" \
--body "$(cat <<'EOF'
Closes #<issue_number>
## Summary
<1-3 bullet points>
## Test plan
<checklist from the issue's Test Plan section>
EOF
)"
PR Body Structure
See PR-TEMPLATE.md for the full template.
Validation Checklist
Before creating a branch or PR, verify:
- Type matches the issue label (
enhancement→feat,bug→fix,chore→chore) - Issue number exists and is open
- Branch is based on latest
main - PR body includes
Closes #<number>
What ships with it
1 file 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.
- 4d ago First seen · 77 lines · 56 tokens per session scan A 0c7619a18268
creating-branches-and-prs is a skill published in the GitHub repository darkcofy/sqlprism (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 558 once invoked, about $0.0003 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…