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 richfrem/agent-plugins-skills --skill github-issue-refactor-proposergit clone --depth 1 https://github.com/richfrem/agent-plugins-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/richfrem/agent-plugins-skills/github-issue-refactor-proposer)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/github-issue-refactor-proposer"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-refactor-proposer/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/richfrem/agent-plugins-skills/github-issue-refactor-proposer"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-refactor-proposer.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.00186 | $0.00828 |
| Opus 5.5 | $0.00074 | $0.00331 |
| Sonnet 5.5 | $0.00037 | $0.00166 |
| Haiku 4.5 | $0.00019 | $0.00083 |
Grade A, and why
github-issue-refactor-proposer 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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Refactor Proposer (github-issue-refactor-proposer)
Consumes friction hotspot reports and synthesizes systemic refactoring proposals for human review regarding recurring Tier 3 architecture friction.
Contents
Critical Constraints
- Synthesis Only: Never autonomously create git branches, write commits, or open pull requests.
- One Proposal Per Root Cause: Group findings by systemic pattern rather than creating omnibus proposals.
- Target Tier 3 Specifically: Focus on systemic architecture debt, recurring multi-component failures, and core design flaws.
Quick start
Inspect active friction hotspots and unresolved Tier 3 issues:
cat references/map-debt.md
Workflow
- Consume Hotspot Reports: Inspect friction cluster analysis and identified Tier 3 architectural debt.
- Consolidate Root Causes: Group related failure symptoms under a single root architectural deficiency.
- Draft Refactoring Proposal: Save proposal to
temp/github-issue-refactor-proposal-<slug>.mddetailing patterns and impact. - Human Review Gate: Present proposal to the user and request explicit authorization before proceeding.
- Delegated Execution: Upon approval, hand off execution to PR lifecycle agents in isolated worktrees.
Related GitHub issue skills
| Skill | Role | Relation |
|---|---|---|
github-issue-agent |
Logs friction and clusters it into hotspots | Produces this skill's input |
github-issue-prioritizer |
Ranks issues P0-P3 | Ranks the issues a proposal covers |
github-issue-resolution-reviewer |
Audits closed issues for recurrence | Flags recurring friction that becomes a proposal |
github-issue-worktree-agent |
Creates .worktrees/issue-NNN |
Workspace for an approved proposal |
github-issue-pr-lifecycle-agent |
Issue to PR to closure | Executes an approved proposal |
github-issue-backlog-agent |
Promotes local tasks to issues | Turns a proposal's follow-ups into issues |
What ships with it
4 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.
- 4d ago First seen · 77 lines · 186 tokens per session scan A cf55a5afe61e
github-issue-refactor-proposer is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 186 tokens to every session and 828 once invoked, about $0.0007 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-10-16.
Other skills, from other repositories
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
conventional-commits
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
skill-security-hooks
Install and maintain defensive security hooks and CI gates for authorized SaaS projects. Use when asked to add pre-commit hooks, pre-push hooks, CI security scans, GitHub Actions hardening, secret scanning, dependency scanning, SAST, DAST gates, or security automation around existing repositories.
collaboration
Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub.
session-start
Use this skill when initializing a session for any project repo. Autonomously analyzes git state, VCS issues, SSOT files, branches, environment, and cross-repo status. Then presents structured findings with recommendations before development wave planning, or an operations contract for explicitly requested…