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.
git clone --depth 1 https://github.com/andrei-isvoran96/claude-skill-labWrote 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/commands/andrei-isvoran96/claude-skill-lab/issue)<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/issue"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/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.00000 | $0.00792 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
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 6d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pick up a GitHub issue: fetch its title/body/labels, create a properly-named branch from origin/<BASE_BRANCH>, check it out, and surface the issue body as context.
Arguments
This command accepts a GitHub issue number as $ARGUMENTS. Example: /issue 207
Steps
-
Validate the argument. If
$ARGUMENTSis empty, not a positive integer, or contains anything other than digits, ask the user to pass a numeric issue number and stop. Do NOT callghwith bogus input. -
Fetch the issue. Run a single
ghcall to pull everything you need:gh issue view $ARGUMENTS --json number,title,body,labels,state,urlIf
gherrors (issue doesn't exist, repo not configured, not authenticated), surface the error verbatim and stop. -
Refuse to work on a closed issue. If
stateisCLOSED, warn the user, print the URL, and stop unless they explicitly say "open it anyway" — closed issues usually mean the work was already done or rejected. -
Pick the branch prefix from labels.
- If any label name (case-insensitive) contains
bug,fix, ordefect→ prefix isbug - Otherwise → prefix is
feature - If the labels list is empty, default to
featureand mention this in the final report so the user can correct it if needed.
- If any label name (case-insensitive) contains
-
Build the slug from the title.
- Lowercase
- Replace any run of non-alphanumeric chars with a single
- - Trim leading/trailing
- - Truncate to 40 characters max, then trim trailing
-again - Example:
"Fix: edges disappear when deleting branched node"→fix-edges-disappear-when-deleting-branche
The branch name is then
<prefix>/<num>-<slug>. Example:bug/207-fix-edges-disappear-when-deleting-branche. -
Sync
<BASE_BRANCH>and create the branch. Run sequentially:git fetch origin <BASE_BRANCH> git checkout -b <branch-name> origin/<BASE_BRANCH>If the branch already exists locally:
- If we're already on it, just
git pull --ff-only origin <BASE_BRANCH>(best-effort, may fail if there are commits — that's fine, just report) and skip to step 7. - Otherwise ask the user whether to switch to it (
git checkout <branch-name>) or abort. Do NOT delete or force-recreate the branch on your own.
- If we're already on it, just
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.
- 6d ago First seen · 64 lines · 0 tokens per session scan A 4c88e8c05148
issue is a command published in the GitHub repository andrei-isvoran96/claude-skill-lab (1 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 792 tokens. 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
next
Suggest the most likely next workflow action based on current context.
weekly-summary
Generate weekly work summary from git activity.