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 ymd38/dev-skills --skill yds-gh-issue-plannergit clone --depth 1 https://github.com/ymd38/dev-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/ymd38/dev-skills/yds-gh-issue-planner)<a href="https://agentmods.dev/skills/ymd38/dev-skills/yds-gh-issue-planner"><img src="https://agentmods.dev/badge/skills/ymd38/dev-skills/yds-gh-issue-planner/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/ymd38/dev-skills/yds-gh-issue-planner"><img src="https://agentmods.dev/badge/skills/ymd38/dev-skills/yds-gh-issue-planner.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.00144 | $0.01229 |
| Opus 5 | $0.00072 | $0.00615 |
| Sonnet 5 | $0.00029 | $0.00246 |
| Haiku 4.5 | $0.00014 | $0.00123 |
Grade A, and why
yds-gh-issue-planner 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 9d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Planner
Overview
Fetch a GitHub Issue, analyze its content, investigate related code in the repository, and present a structured response plan to the user. After the user confirms, post the agreed plan as a comment on the issue. Implementation and PR creation are out of scope — use yds-gh-issue-resolver for those steps.
Workflow
Step 1: Fetch the Issue
Run the following command (replace <id> with the issue number):
gh issue view <id> --json number,title,body,labels,assignees,state,url,comments
If no repository context is clear, also run:
gh repo view --json nameWithOwner
Extract from the response:
- Title and body: the core problem statement
- Labels: bug / feature / enhancement / etc. — determines response approach
- Comments: additional context, workarounds, or constraints from stakeholders
Pre-scoped Issues: if the body contains <!-- gh-issue-drafter:scoped-issue -->,
the Issue was drafted via yds-gh-issue-drafter and its scope is author-approved. Treat its
sections as binding input to the plan:
- 完了条件 (Done) — the contract the plan must satisfy; every condition must be covered by an implementation step or a test in the plan
- 触らない範囲 (Out of scope) — hard boundaries; reject any plan direction that crosses them
- 設計方針 (Design constraints) — constraints on how, not just what
Do not re-ask the user about scope that these sections already answer — raise open questions only for genuinely new information discovered during investigation.
Step 2: Classify the Issue
Determine issue type to guide the investigation strategy:
| Label / Signal | Type | Investigation Focus |
|---|---|---|
| bug, error, crash | Bug fix | Error paths, edge cases, affected callers |
| feature, enhancement | New feature | Insertion points, interface contracts, related modules |
| refactor, tech-debt | Refactoring | Current usage sites, test coverage |
| docs, documentation | Docs update | Existing docs, code references |
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.
- 9d ago First seen · 136 lines · 144 tokens per session scan A fc3746d1265d
yds-gh-issue-planner is a skill published in the GitHub repository ymd38/dev-skills (4 stars, last pushed yesterday), licensed MIT. It adds 144 tokens to every session and 1,229 once invoked, about $0.0007 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-launch-checklist
Audits a project for hiring visibility before going public. Verifies README clarity for impatient hiring managers, checks evaluation setup, tests, CI/CD, config file, and deployment link. Generates a pre-launch audit report with gaps and priorities. Use when you're ready to make a project visible to hiring managers or…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.