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.
curl -O https://raw.githubusercontent.com/pvliesdonk/scholar-mcp/main/.agents/skills/authoring-issues-prs/SKILL.mdgit clone --depth 1 https://github.com/pvliesdonk/scholar-mcpWrote 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/pvliesdonk/scholar-mcp/authoring-issues-prs)<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.
<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>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.02033 |
| Opus 5.5 | $0.00034 | $0.00813 |
| Sonnet 5.5 | $0.00017 | $0.00407 |
| Haiku 4.5 | $0.00009 | $0.00203 |
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 26d 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.
This is a copy
100% identical to authoring-issues-prs — 110 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.
How it starts
The opening of the file, as written. The whole thing — 178 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.
- "Agent-authored posts" — the footer every post ends with, and how to read earlier posts under the account holder's name (step 7).
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 onpvliesdonk/fastmcp-pvl-core. - A template-owned file — workflows,
Dockerfile, theserver.pyskeleton, anythingcopier updatere-renders — → template: file onpvliesdonk/fastmcp-server-template. - Anything inside a
DOMAIN-*/CONFIG-*/PROJECT-*sentinel block, ortools.py/resources.py/prompts.py/domain.py/tests/→ domain: file on this repository.
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.
- 26d ago Changed · +8 lines 52530c9123d2
- 1mo ago Changed · +27 lines cc91cf486d0e
- 1mo ago First seen · 143 lines · 86 tokens per session scan A 539b6aab8e11
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 2,033 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to authoring-issues-prs, differing in 110 lines, and is treated as a copy.
Other skills, from other repositories
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.
gitlab-discovery
Find a GitLab project or namespace and establish the exact target for follow-up repository, merge request, work-item or CI work. Use for GitLab project discovery, not local filesystem search or GitHub repositories.
cor-api-tools
Deep reference for all 61 COR MCP API tools — complete argument listings, JSON request/response examples, and common usage patterns for every module.