What is authoring-issues-prs?

A guide for writing GitHub issues, tickets, and pull requests in a specific repository. It uses that repository's contribution rules to decide how and where a change should be recorded.

Preparing bug reports, review findings, epics, tickets, and pull requests after checking the repository's contribution guidelines.

It helps avoid incorrectly routed reports, vague issue descriptions, and pull requests that do not follow the project's process.

How pvliesdonk/scholar-mcp configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to pvliesdonk/scholar-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/pvliesdonk/scholar-mcp/main/.agents/skills/authoring-issues-prs/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/pvliesdonk/scholar-mcp

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pvliesdonk/scholar-mcp/authoring-issues-prs/github.svg)](https://agentmods.dev/skills/pvliesdonk/scholar-mcp/authoring-issues-prs)

Your own site

<a href="https://agentmods.dev/skills/pvliesdonk/scholar-mcp/authoring-issues-prs"><img src="https://agentmods.dev/badge/skills/pvliesdonk/scholar-mcp/authoring-issues-prs/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pvliesdonk/scholar-mcp/authoring-issues-prs"><img src="https://agentmods.dev/badge/skills/pvliesdonk/scholar-mcp/authoring-issues-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,493 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00086	$0.01493
Opus 5	$0.00043	$0.00746
Sonnet 5	$0.00017	$0.00299
Haiku 4.5	$0.00009	$0.00149

Measured 10d ago against content hash 539b6aab8e11, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

authoring-issues-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 10d 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.

Origin

This is a copy

100% identical to authoring-issues-prs — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/authoring-issues-prs/SKILL.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Authoring issues and pull requests

CONTRIBUTING.md at the repository root is the single source for the rules: issue voice, uncertainty markers, one-issue-one-problem, PR discipline, and the three-tier routing. This skill adds only what a document cannot — the trigger, the order of operations, and the API mechanics for the steps issue forms cannot perform. It deliberately does not restate the rules; a second copy would drift from the file silently.

Procedure

1. Read CONTRIBUTING.md — now, not from memory

Read CONTRIBUTING.md (repository root) before drafting a single sentence, even if you believe you remember it. You are about to apply these sections, and their exact wording matters:

"Observation, not work order" and "The uncertainty rule" — issue voice and the [verified: how] / [unverified] markers.
"One issue, one observed problem" and the "Remove before posting" table — run your draft through the table before submitting.
"Pull requests" — no orphan PRs, the deliberately-does-not section.
"Where to send fixes" — the routing walked in step 2.

If anything in this skill appears to conflict with CONTRIBUTING.md, the file wins.

2. Route before writing

Decide the repo first, then write for that repo. The test: which file would a fix change?

Anything you'd change in fastmcp_pvl_core → library: file on pvliesdonk/fastmcp-pvl-core.
A template-owned file — workflows, Dockerfile, the server.py skeleton, anything copier update re-renders — → template: file on pvliesdonk/fastmcp-server-template.
Anything inside a DOMAIN-* / CONFIG-* / PROJECT-* sentinel block, or tools.py / resources.py / prompts.py / domain.py / tests/ → domain: file on this repository.

CONTRIBUTING.md's "Where to send fixes" defines these tiers with the post-merge propagation for each. When the tier is genuinely unclear, say so in the issue with an [unverified] marker instead of guessing silently.

Read the full file on GitHub · 143 lines

Changes

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.

10d ago First seen · 143 lines · 86 tokens per session scan A 539b6aab8e11

Subscribe to this mod's changes

authoring-issues-prs is a skill published in the GitHub repository pvliesdonk/scholar-mcp (2 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,493 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to authoring-issues-prs, differing in 0 lines, and is treated as a copy.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

scholar-mcp: Skill for Claude Code