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/guillermoscript/lms-front/work-issuenpx skills add guillermoscript/lms-front --skill work-issuegit clone --depth 1 https://github.com/guillermoscript/lms-frontWhat 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 | $0.00134 | $0.04444 |
| Opus 5 | $0.00067 | $0.02222 |
| Sonnet 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 2d 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.
- 2d 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 (24 stars, last pushed 2d ago), licensed MIT. It adds 134 tokens to every session and 4,444 once invoked, about $0.0007 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
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…
apple-design
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading)…
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
add-landing-template
Add a new org landing-page template to the ClassroomIO monorepo. Use when the user asks to "create/add a new landing template", "add a new template like X to the org landing pages", "build a new theme for the org landing page", or hands over a design reference (image, URL, prototype) for a new landing visual style.
animation-vocabulary
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and…
prototype
Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.