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 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/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/tomzx/agents/check-issue-status"><img src="https://agentmods.dev/badge/skills/tomzx/agents/check-issue-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 122 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.03310 |
| Opus 5.5 | $0.00046 | $0.01324 |
| Sonnet 5.5 | $0.00023 | $0.00662 |
| Haiku 4.5 | $0.00012 | $0.00331 |
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 8d 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 — 322 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. It inspects the current checkout when it is the target repository, and clones the repository on demand when it is not. Use before starting work, or to find 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.- Network access when the repository still has to be cloned (step 1).
- 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.
Communication guidelines (outbound text)
Before composing any text posted or drafted on the user's behalf, apply communication-guidelines/SKILL.md.
Steps
1. Resolve the code checkout
Code inspection needs a checkout of the target repository. Use the current checkout when it is the target repository, and clone the repository when it is not.
Resolve the current directory's repository:
git remote get-url origin
Record its {owner}/{repository} as CWD_REPO.
If the command fails (no git repository, or no origin remote), treat it as no match and clone.
- If
CWD_REPOmatches$REPO(case-insensitive), setWORK_DIRto the current directory. Rungit status --porcelain; if the tree has uncommitted changes, note it in the report, since the evidence may not match the published code. - Otherwise clone the repository into a cache directory and set
WORK_DIRto it, reusing a previous clone when one exists:
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.
- 8d ago Changed · +44 lines a4a82b1bc904
- 22d ago Changed · +33 lines 6760136d3426
- 24d ago Changed 6dc5121ab86d
- 27d ago Changed f5ffc0ed6a8c
- 28d ago Changed · +4 lines 78509c810b17
- 2mo 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 (13 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 3,310 once invoked, about $0.0005 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.