Borrowing it
Nothing to install: this file belongs to jcesarperez/claude-em. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jcesarperez/claude-em/main/.claude/skills/check-issue/SKILL.mdgit clone --depth 1 https://github.com/jcesarperez/claude-emWrote 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/jcesarperez/claude-em/check-issue)<a href="https://agentmods.dev/skills/jcesarperez/claude-em/check-issue"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/check-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.00069 | $0.03554 |
| Opus 5 | $0.00034 | $0.01777 |
| Sonnet 5 | $0.00014 | $0.00711 |
| Haiku 4.5 | $0.00007 | $0.00355 |
Grade A, and why
check-issue 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool
Run this script using the Bash tool:
bash .claude/skills/check-issue/scripts/fetch_issue.sh <ISSUE_KEY> --json
ISSUE_KEY: any issue key (Story, Bug, Task, Sub-task)- If the issue is not found, the script exits with an error. Report it and stop.
The script outputs JSON with this structure:
{
"fetched_at": "2026-04-20T10:00:00Z",
"issue": {
"key": "FBX-1234",
"issuetype": "Story",
"summary": "...",
"status": "In Review",
"statusCategory": "In Progress",
"description": "plain text",
"assignee": "Name or null",
"priority": "High",
"duedate": "YYYY-MM-DD or null",
"created": "...",
"updated": "...",
"comments": [{ "author": "Name", "created": "...", "body": "plain text" }],
"time_in_current_status": { "formatted": "Xd Yh Zm", "seconds": 0, "since": "..." },
"first_in_progress_at": "YYYY-MM-DDTHH:MM:SSZ or null",
"cycle_time": { "formatted": "Xd Yh Zm", "seconds": 0 }, // Done issues only, or null
"time_in_progress": { "formatted": "Xd Yh Zm", "seconds": 0 }, // In Progress issues only, or null
"status_transitions": [{ "from": "...", "to": "...", "at": "...", "author": "Name" }],
"assignee_changes": [{ "from": "...", "to": "...", "at": "...", "changed_by": "Name" }],
"pr": {
"count": 2,
"open_count": 1,
"draft_count": 0,
"items": [ // null if only aggregate data is available
{
"id": "#123",
"title": "fix: FBX-1234 ...",
"status": "OPEN", // OPEN | DRAFT | MERGED | DECLINED | CLOSED
"open": true, // true only when status == OPEN (ready for review)
"author": "Name",
"branch": "FBX-1234-my-branch",
"last_updated": "YYYY-MM-DDTHH:MM:SS.000+0000",
"url": "https://github.com/..."
}
]
} // or null if no PRs found
"pr_merge_gap": { "formatted": "Xd Yh Zm", "seconds": 0 } // gap between first and last MERGED PR; null if < 2 merged PRs
},
"parent_epic": { "key": "FBX-1000", "summary": "...", "status": "In Development" }, // or null
"subtasks": [
{
"key": "FBX-1235",
"summary": "...",
"status": "In Progress",
"statusCategory": "In Progress",
"assignee": "Name or null",
"time_in_current_status": { "formatted": "Xd Yh Zm", "seconds": 0, "since": "..." }
}
],
"pingpong": {
"status_bounces": 0,
"assignee_change_count": 0,
"pingpong_comment_count": 0,
"comment_author_count": 0,
"detected": false
}
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 319 lines · 69 tokens per session scan A 2240c491eebb
check-issue is a skill published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 3,554 once invoked, about $0.0003 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-30.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
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.