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 agentmods add skills/youngjaedev/my-claude-plugins/resolve-issuenpx skills add YoungjaeDev/my-claude-plugins --skill resolve-issuegit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWrote 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/youngjaedev/my-claude-plugins/resolve-issue)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/resolve-issue"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/resolve-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.00166 | $0.05369 |
| Opus 5 | $0.00083 | $0.02684 |
| Sonnet 5 | $0.00033 | $0.01074 |
| Haiku 4.5 | $0.00017 | $0.00537 |
Grade B, and why
resolve-issue scanned grade B with 1 finding 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat > .claude/state/github-dev-${ISSUE_NUMBER}.json << 'EOF' How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve GitHub Issue
Act as an expert developer who systematically analyzes and resolves GitHub issues. Receive a GitHub issue number as argument and resolve the issue. Follow project guidelines in @CLAUDE.md.
Prerequisites
Before starting the workflow:
- Serena MCP: If not already active, run
activate_projectto enable semantic code analysis tools - Clean state: Ensure no uncommitted changes that could conflict with the new branch
Flags
| Flag | Description |
|---|---|
--skip-review |
Skip 2-stage review (for trusted changes) |
--strict |
Treat lint failures as blocking errors |
--skip-cr-fix |
Skip the auto cr-fix loop after PR creation (default: cr-fix runs) |
--cr-fix-max <n> |
Cap iterations on the auto cr-fix loop (default: 5) |
--auto-merge |
Pass through to cr-fix; auto-merge the PR after convergence (default: OFF) |
--codex-grace <sec> |
Pass through to cr-fix; extra wait window after CodeRabbit completes for ChatGPT-Codex review comments (default: 90) |
--no-codex |
Pass through to cr-fix; force-disable Codex auto-detect for the run (default: auto-detect ON) |
--skip-minor |
Pass through to cr-fix; silently skip CR Minor/Trivial/Info severity (excluding Bug/Security) + Codex P2 to shrink the gated queue on lint-heavy PRs |
--no-minor-stop |
Pass through to cr-fix; disable the minor soft-stop (default ON — cr-fix stops from iter 2 when a cycle applied only low-severity fixes with nothing deferred, final_state=minor_floor) |
--no-generalize |
Pass through to cr-fix; disable bounded same-file generalization (default ON — a real + high-confidence + grep-able finding also patches sibling occurrences of the same pattern in the same file) |
--cr-source <mode> |
Pass through to cr-fix; review source selector. auto (default) falls back to local coderabbit CLI or Codex-only on PR-bot rate-limit. pr-bot / cli / codex-only lock the source. |
Note: For parallel development, create worktrees manually before starting Claude sessions. See CLAUDE.md for the recommended worktree workflow.
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.
- today Changed · -1 tokens per session 54d1d25c2429
- 5d ago First seen · 402 lines · 167 tokens per session scan B 2dfd62dd932b
resolve-issue is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 166 tokens to every session and 5,369 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…