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 skills add Mark-Life/agent-skills --skill pr-issuegit clone --depth 1 https://github.com/Mark-Life/agent-skillsWrote 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/mark-life/agent-skills/pr-issue)<a href="https://agentmods.dev/skills/mark-life/agent-skills/pr-issue"><img src="https://agentmods.dev/badge/skills/mark-life/agent-skills/pr-issue.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.1 | $0.00034 | $0.01866 |
| Opus 5 | $0.00017 | $0.00933 |
| Sonnet 5 | $0.00007 | $0.00373 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
pr-issue 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 6d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR & Issue
Write the title and body Vim-style — area: summary, then labelled sections
in template order.
Three words carry this skill. Symptom: every body opens with the thing a human noticed. Mechanism: the next paragraph names the exact code that misbehaves. Receipts: any output shown was really produced, never output that would plausibly have been produced — and a change to rendered output shows that output.
A PR is read once, in a hurry, by someone deciding whether to approve. An issue is read once, weeks later, by someone deciding whether to work on it — and again by whoever picks it up. Every sentence earns its place by moving that decision along.
Which artifact
A PR argues that a change should land. An issue argues that a change is needed.
The title, the Problem section, and the style rules are shared; everything
after them diverges.
| Pull request | Issue / ticket | |
|---|---|---|
| Title mood | imperative — the change | indicative — the defect or the gap |
| Header block | none | Labels: / Relates to: |
| Body | Problem, Solution, Security Impact, Testing | Problem, Reproduction, Expected vs actual, Proposed solution |
| Evidence | commands you ran, output you copied | steps that reproduce, revision the line numbers pin to |
| Tone of the fix | decided | proposed, with the open questions named |
Read one reference, now, before drafting. This file carries only what both artifacts share.
Shared steps
- Gather the ground truth in full. For a PR that is the diff
(
git diff <base>...HEAD), read until every changed file is accounted for, not until the shape is clear. For an issue it is the code path that fails, read until you can name the line that decides the wrong outcome. - One artifact, one problem. A diff spanning unrelated areas splits into two PRs; a report bundling two defects splits into two issues.
- Draft the title from the area of the largest coherent change.
- Follow the reference for the artifact — it owns the middle of the body.
- Cut every clause that would not change what the reader does. Done when the body is under 400 words.
- Open it with a heredoc, so the markdown survives the shell:
What ships with it
2 files 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.
- 6d ago First seen · 178 lines · 34 tokens per session scan A c09e927aa7b2
pr-issue is a skill published in the GitHub repository Mark-Life/agent-skills (2 stars, last pushed 22d ago), licensed MIT. It adds 34 tokens to every session and 1,866 once invoked, about $0.0002 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
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
security-ownership-map
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for…
commit-with-reflection
A Git workflow that creates a Chinese-language report about debugging mistakes, investigation steps, fixes, and lessons learned, then includes that report in a commit. Git is a system for tracking changes to code.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
manuscript-as-code
Treat manuscripts as software: version control, reproducible builds, figure pipelines, CI, and structured repo layout. Helps teams avoid 'finalv7' chaos and ensures submission-ready artifacts.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.