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 GktuOktay/ai-skills --skill git-issue-managergit clone --depth 1 https://github.com/GktuOktay/ai-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/gktuoktay/ai-skills/git-issue-manager)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/git-issue-manager"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/git-issue-manager/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/gktuoktay/ai-skills/git-issue-manager"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/git-issue-manager.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.00062 | $0.00618 |
| Opus 5.5 | $0.00025 | $0.00247 |
| Sonnet 5.5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
Git Issue Manager 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 1mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Issue Management Guide
This skill outlines the best practices for managing issues, writing effective bug reports and feature requests, and streamlining the triage process.
Writing Effective Bug Reports
A good bug report helps developers reproduce and fix the issue quickly.
Essential Components
- Title: Clear and concise summary of the issue.
- Environment: OS, Browser, App Version, etc.
- Reproduction Steps: Step-by-step instructions to reproduce the bug.
- Expected Behavior: What should happen.
- Actual Behavior: What actually happens.
- Visual Proof: Screenshots, videos, or logs (if applicable).
Example
Title: Search bar returns 500 error when special characters are used Steps to Reproduce:
- Go to the homepage.
- Enter
%$#@in the search bar. - Click "Search". Expected: A "No results found" message or input validation error. Actual: The page crashes and displays a 500 Internal Server Error.
Writing Feature Requests
Feature requests should clearly state the problem and the proposed solution.
Essential Components
- Problem Statement: What is the problem or limitation?
- Proposed Solution: How should the feature work?
- Alternatives Considered: What other options were evaluated?
- Additional Context: Any other information, like mockups or use cases.
Labeling Strategy
Use a consistent labeling strategy to categorize and prioritize issues.
Common Label Categories
- Type:
bug,enhancement,documentation,question - Priority:
high,medium,low,critical - Status:
triage,in-progress,blocked,needs-review - Scope/Component:
frontend,backend,database,ui
Triage Process
- Review New Issues: Read through incoming issues regularly.
- Reproduce: Verify if bugs are reproducible.
- Labeling: Apply appropriate type, priority, and scope labels.
- Assignment: Assign the issue to a team member or milestone.
- Link to PRs: Ensure developers link pull requests to the issue using keywords (e.g.,
Fixes #123).
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.
- 1mo ago First seen · 65 lines · 62 tokens per session scan A 53a4d8631232
Git Issue Manager is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 618 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
task
AI DevKit · Track dev-lifecycle / dev-debug progress on a durable task with the ai-devkit task CLI. Use to record phase, progress, next step, blockers, and validation evidence.
conductor-new-track
Create a new track with specification and phased implementation plan.
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
dev-retro
AI DevKit · Run an evidence-based retrospective on finished work (feature, session, incident) and turn friction into durable fixes, automation first. Use when users ask for a retro, lessons learned, post-mortem, or "what went wrong", or when another skill offers one after a feature or fix.