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/tomzx/agents/check-issue-statusnpx skills add tomzx/agents --skill check-issue-statusgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/check-issue-status)<a href="https://agentmods.dev/skills/tomzx/agents/check-issue-status"><img src="https://agentmods.dev/badge/skills/tomzx/agents/check-issue-status.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.00116 | $0.02704 |
| Opus 5 | $0.00058 | $0.01352 |
| Sonnet 5 | $0.00023 | $0.00541 |
| Haiku 4.5 | $0.00012 | $0.00270 |
Grade A, and why
check-issue-status 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 5d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Issue Status
Determines whether a GitHub issue is already addressed in the codebase. Reads the issue, extracts the behavior it requests in whatever format it is written, and inspects the code to verify whether that behavior is already present. Use before starting work, or to surface stale issues that can be closed.
This skill inspects code, not GitHub metadata.
For duplicate issues and existing fix PRs use check-duplicates.
To actually trigger a reported bug at runtime, use reproduce-issue.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, target the issue from
$ISSUE_NUMBER(and$REPO). ghCLI authenticated with read access to the target repository.- The current working directory is a checkout of the target repository (this skill reads code).
- A GitHub issue number describing a feature request, a bug, or a task.
Skill attribution (GitHub)
Before posting to GitHub, read ../github-post-attribution/SKILL.md and append the footer for SKILL_DIR = check-issue-status.
Steps
1. Fetch the issue
Fetch the issue to understand what it asks for:
ghx issue view $ISSUE_NUMBER --repo $REPO
Read any files present under .sdlc/context/ (architecture.md, vocabulary.md, conventions.md) for context that helps locate the relevant code.
If the working directory is not a checkout of $REPO (different git remote get-url origin), warn the user and stop, since code evidence would be from the wrong repository.
2. Classify the issue
Decide which of these the issue is:
- Feature request: asks for new behavior or a capability to exist.
- Bug report: states that existing behavior is wrong and should be different.
- Other (question, task, refactor): treat the desired end state as the behavior to verify.
Record the classification. It only changes how evidence is framed, not the procedure.
3. Extract behavioral claims
Issues arrive in many formats: formal acceptance criteria, prose, screenshots, error logs, checklists, or a single sentence. Do not assume a structure. Read the whole body and distill 1 to N discrete behavioral claims, each a single testable assertion about what the code should do.
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.
- 5d ago First seen · 241 lines · 116 tokens per session scan A f86123462dc2
check-issue-status is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 2d ago), licensed MIT. It adds 116 tokens to every session and 2,704 once invoked, about $0.0006 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
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-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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…