Borrowing it
Nothing to install: this file belongs to Luqueee/kivgraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Luqueee/kivgraph/main/.claude/skills/opening-pull-requests/SKILL.mdgit clone --depth 1 https://github.com/Luqueee/kivgraphWrote 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/luqueee/kivgraph/opening-pull-requests)<a href="https://agentmods.dev/skills/luqueee/kivgraph/opening-pull-requests"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/opening-pull-requests/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/luqueee/kivgraph/opening-pull-requests"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/opening-pull-requests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.01377 |
| Opus 5.5 | $0.00028 | $0.00551 |
| Sonnet 5.5 | $0.00014 | $0.00275 |
| Haiku 4.5 | $0.00007 | $0.00138 |
Grade A, and why
opening-pull-requests 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opening a Kivgraph pull request
The completion condition
Opening the GitHub page is not completion. A PR is ready only when all of these describe its latest head commit:
- the intended changes are committed and pushed;
- the relevant local gates have passed;
- required GitHub checks have completed successfully;
- CodeRabbit has completed its review of that head;
- every still-valid actionable finding has been addressed or explicitly explained;
- GitHub reports no merge conflict or other known merge blocker.
Every push makes earlier CI and bot conclusions stale. Wait again after each feedback commit.
Branch naming
When creating a new branch, use a conventional type followed by one short, lowercase, kebab-case description. Release branches are the one exception: they retain the dotted SemVer so the branch maps directly to its release tag.
feat/add-python-loader
fix/daemon-path-sync
docs/harden-release-skill
test/cover-registry-publish
ci/update-release-gate
chore/refresh-tool-manifest
release/v1.2.3
Use feat, fix, docs, refactor, test, ci, build, perf, chore,
or release as appropriate. Never prefix a branch with the agent, model,
client, or automation name, including codex/. Keep the name specific to the
change, avoid spaces and ticket-only names, and include a ticket identifier
only when it improves traceability, preserving the repository's canonical
spelling for that identifier.
Apply this convention only when creating a branch. If an existing PR already uses another name, keep its head branch while updating it; do not rename, delete, or recreate it as a side effect of ordinary PR work.
Before pushing a new branch, check the complete remote head-ref namespace. An existing ancestor or descendant ref also blocks the name, even when the exact name is unused:
branch="$(git symbolic-ref --short HEAD)" || {
echo "cannot determine current branch" >&2
exit 1
}
refs="$(git ls-remote --heads origin)" || {
echo "cannot read remote branch refs from origin" >&2
exit 1
}
conflict=""
while IFS= read -r line; do
[ -n "$line" ] || continue
ref="${line#*refs/heads/}"
case "$ref" in
"$branch"|"$branch"/*) conflict="$ref"; break ;;
esac
case "$branch" in
"$ref"|"$ref"/*) conflict="$ref"; break ;;
esac
done <<<"$refs"
if [ -n "$conflict" ]; then
echo "remote branch namespace conflict: $conflict" >&2
exit 1
fi
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 Changed · +59 lines f62a28138efe
- 2mo ago First seen · 86 lines · 71 tokens per session scan A 5d1827866238
opening-pull-requests is a skill published in the GitHub repository Luqueee/kivgraph (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 1,377 once invoked, about $0.0003 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
codestory-grounding
Use when discovering repository structure, tracing relationships, analyzing change impact, or validating CodeStory retrieval or an installed plugin through the CodeStory plugin MCP. Skip only for bounded inspection or editing of named files that does not require those operations.
code-knowledge-graph
Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
memtrace-style-fingerprint
Pull the codebase's empirical style norm from Memtrace and match it when writing or editing source code in an indexed repo. Use when choosing between competing idioms (ternary vs if-else, arrow vs function declaration, const vs let, await vs .then, early-return vs nested-return), matching naming case, or when the user…
memtrace-refactoring-guide
Build a phased, risk-scored refactoring plan from Memtrace complexity, dead-code, bridge, impact analysis, and Cortex decision-memory constraints. Use when the user wants to refactor source code, reduce complexity, clean technical debt, delete dead code, split large functions, extract modules, reorganize code, or…
cartograph
Explore a codebase through Cartograph v2's native RocksDB code graph: intent-aware context, exact/BM25/hybrid search, callers/callees/impact, affected tests, live source, review, freshness, and bounded index administration.