Borrowing it
Nothing to install: this file belongs to guillermoscript/lms-front. 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/guillermoscript/lms-front/master/.agents/skills/work-issue/SKILL.mdgit clone --depth 1 https://github.com/guillermoscript/lms-frontWrote 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/guillermoscript/lms-front/work-issue)<a href="https://agentmods.dev/skills/guillermoscript/lms-front/work-issue"><img src="https://agentmods.dev/badge/skills/guillermoscript/lms-front/work-issue/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/guillermoscript/lms-front/work-issue"><img src="https://agentmods.dev/badge/skills/guillermoscript/lms-front/work-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00134 | $0.04444 |
| Opus 5.5 | $0.00054 | $0.01778 |
| Sonnet 5.5 | $0.00027 | $0.00889 |
| Haiku 4.5 | $0.00013 | $0.00444 |
Grade A, and why
work-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 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Issue — issue URL to reviewed PR
Automates the full issue-to-PR pipeline for whatever GitHub repo the current working directory belongs to. The user pastes an issue URL (or number); you deliver a merged-ready PR with the project board, labels, milestone, and QA record all handled. Every step exists because a human reviewer or QA person consumes its output later — the issue comment is the public record of the approach, the PR body is the QA script, the GIF is the visual proof. Write those artifacts for them, not for the user in this chat.
This skill is the orchestrator: it owns the pipeline order, the implementation (the only phase no companion covers), and the wrap-up. The rest lives in six companion skills, each also usable standalone — invoke them via the Skill tool at the step that needs them, and follow their rules rather than restating them here:
| Skill | Owns | Used at |
|---|---|---|
gh-repo-config |
Repo facts, conventions, .claude/gh-workflow.config.json |
Step 0 |
issue-plan |
Read issue → survey → plan → assign + In Progress + plan comment | Step 2 |
gh-board |
All GitHub Projects (v2) operations (board.sh) |
via issue-plan/ship-pr |
ui-evidence |
Before/after screenshots, GIF recording, PR media upload | Steps 2, 4, 6 |
ship-pr |
PR body, draft→ready lifecycle, metadata, Slack announcement, post-merge close-out | Steps 5–7 + close-out |
pr-review-loop |
Poll the PR for review feedback, address it, merge on approval, trigger close-out, clean up the worktree/branch | Step 8 |
Invocation and +skill params
The argument is the issue (URL, #N, or bare number), optionally followed by
extra skills prefixed with +:
/work-issue https://github.com/<owner>/<repo>/issues/302
/work-issue #302 +shadcn +animate
/work-issue 302 +systematic-debugging
Each +name is a skill to load in Step 1 in addition to the defaults.
This is the extension point: the user will keep adding skills to their
toolbox over time, so treat the list as open-ended. If a +name doesn't
match any available skill, say so briefly and continue without it — a typo
shouldn't sink the run.
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.
- 1mo ago First seen · 328 lines · 134 tokens per session scan A 2daa871614ca
work-issue is a skill published in the GitHub repository guillermoscript/lms-front (40 stars, last pushed today), licensed MIT. It adds 134 tokens to every session and 4,444 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-30.
Other skills, from other repositories
herdr-kit-workflows
Set up and operate Herdr Kit safely: install and configure the plugin and Mastra Code integration, manage Review and Work repository scope, open primary repository workspaces, synchronize managers, materialize or dematerialize managed worktrees, and update Herdr Kit settings or shortcuts.
herdr-manager-query
Query the authoritative global Herdr Review and Work Manager inventory, recommend actionable PR work, and explicitly materialize confirmed remote-only Review Manager records through the plugin's stable public CLI.
tuturuuu-agent-coordination
Coordinate Tuturuuu multi-agent programs, exact-head evidence, shared-worktree ownership, and handoffs.
summarize-activity
Summarize engineering activity in classroomio/classroomio between two dates — merged PRs, still-open PRs opened in that window, and their demo videos — into a markdown report. Use when the user asks what shipped, what happened, or for a summary/recap/digest of engineering work over a date range.
stage-and-commit
Stage changed files and create a commit following the repo's translation, formatting, and git workflow rules. Use when the user asks to stage, commit, or both.
tuturuuu-platform
Implement Tuturuuu web routes and shared UI, including translations, navigation, and internal API access.