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 pedroiff0/awesome-skills --skill github-issue-pr-attribsgit clone --depth 1 https://github.com/pedroiff0/awesome-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/pedroiff0/awesome-skills/github-issue-pr-attribs)<a href="https://agentmods.dev/skills/pedroiff0/awesome-skills/github-issue-pr-attribs"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/github-issue-pr-attribs/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/pedroiff0/awesome-skills/github-issue-pr-attribs"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/github-issue-pr-attribs.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.00064 | $0.01775 |
| Opus 5 | $0.00032 | $0.00888 |
| Sonnet 5 | $0.00013 | $0.00355 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade A, and why
github-issue-pr-attribs 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 8d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standardize GitHub Issue/PR Metadata + Strong Code Review
Turn ad-hoc issues/PRs into a coherent, repeatable workflow. This skill covers the seven standard assignment fields for both issues and PRs, ships copy-paste issue forms and a PR template, and provides a strong, organized code-review model (fixed comment structure, severity table, per-category rubrics).
Use it when a repo has no templates, reviews are inconsistent, or the user asks to "padronizar issue/PR", "atribuições em issue e PR", "melhorar o code review", or "criar template de issue/PR".
When to Use
- Repo lacks
.github/ISSUE_TEMPLATE/*.ymlorPULL_REQUEST_TEMPLATE.md. - Issues/PRs opened with missing assignee, labels, project, or milestone.
- Code review is unstructured / freeform and hard to scan.
- User wants a reusable standard other agents can apply.
The Seven Standard Assignment Fields
Apply all seven to every issue and PR. API limits noted below.
| Field | Issue | PR |
|---|---|---|
| Assignee | ✅ (who owns it) | ✅ |
| Reviewer | n/a on issue (set on PR) | ✅ |
| Labels | ✅ | ✅ (inherit issue + type) |
| Project | ✅ (Projects V2) | ✅ |
| Milestone | ✅ (Backlog or semver) | ✅ (same as issue) |
| Development | n/a on issue | ✅ (branch↔issue link) |
| Relationship | parent/child links | Fecha # / Relaciona # |
API reality check (gh / REST)
gh issue createsets:--assignee,--label,--milestone,--project,--body,--title. No reviewer on issues.gh pr createsets:--assignee,--label,--milestone,--project,--head,--base,--title,--body,--reviewer(orgh pr edit --add-reviewer).- Projects V2 are NOT settable via REST
gh issue/pr create --projectreliably when the project is V2 (REST targets legacy Projects v1 and 404s). Use the GraphQL mutationaddProjectV2ItemByIdto attach a V2 project item after creation. Seereferences/projects-v2.md. - Self-review request: a single-owner private repo can't formally request review from the same account; document the reviewer in the PR template/body instead.
- Development link: opening a PR from a branch whose name references the issue (or
Fecha #Nin body) auto-links; the GitHub UI shows it under "Development" on the issue.
What ships with it
7 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.
- 8d ago First seen · 115 lines · 64 tokens per session scan A fbf017c83566
github-issue-pr-attribs is a skill published in the GitHub repository pedroiff0/awesome-skills (1 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,775 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-08-31.
Other skills, from other repositories
01-sdlc
Autonomously orchestrates a request from framing to a draft pull request, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for running one development step.
dx-roaster
Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked…
00-async-dev
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a…
fable-validate-loop
Use when the user asks to validate a GitHub issue with Fable 5.1 and then autonomously drive it to a reviewed PR in one shot — "fable-validate-loop", "fable validate and work on.
mnemosyne-maintenance
Use when: upgrading Mnemosyne, diagnosing slow/hung consolidation (mnemosynesleep), fixing missing embeddings, or troubleshooting import/version mismatches.