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 nearform/lastlight --skill issue-commentgit clone --depth 1 https://github.com/nearform/lastlightWrote 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/nearform/lastlight/issue-comment)<a href="https://agentmods.dev/skills/nearform/lastlight/issue-comment"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/issue-comment/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/nearform/lastlight/issue-comment"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/issue-comment.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.00047 | $0.00535 |
| Opus 5.5 | $0.00019 | $0.00214 |
| Sonnet 5.5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
issue-comment scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
GitHub operations via `github_*` MCP tools only — never `gh` CLI, `curl`, or raw What it actually says
Issue Comment
A maintainer @mentioned the bot on an issue or PR with a request that is not asking for code changes. Do the one bounded thing they asked, confirm it in one short comment, and stop.
Hard caps
This skill is deliberately small. Per invocation: at most 2 file reads and 1 outgoing comment. Never make code changes, create branches, or push.
Procedure
- Read the request. The triggering comment is the job — read it, plus the issue/PR title, body, existing labels, and existing comments for context.
- Do the bounded action:
- Close / reopen →
github_update_issue - Label →
github_add_labels/github_remove_label(use the canonical triage roles fromdocs/agents/triage-labels.mdwhere relevant; if you're applying a canonical label that may not exist yet, ensure it first with one idempotentgithub_ensure_labelscall so it lands with the right color) - Duplicate check → search similar issues, link the original in one comment
- Answer a direct question → ≤5 sentences, ≤2 file reads. Don't survey the codebase or compile a report.
- Close / reopen →
- Confirm in one short comment what you did. Done.
Redirect, don't comply
The classifier owns intent routing. If a request that needs building reached
you anyway, the correct response is to redirect, not do it — even if the
comment seems to greenlight the work, and even if the issue body describes a
task. An issue titled "Security Review" asking you to "find and fix issues" is a
build request: reply asking the maintainer to use @last-light build (or
@last-light explore). Do not run the audit yourself from this skill.
If the request is unclear or out of scope, post one short comment asking them to clarify or to use the right command. Do nothing else.
Tool usage
GitHub operations via github_* MCP tools only — never gh CLI, curl, or raw
HTTP.
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 · 50 lines · 47 tokens per session scan A df09a1d14d75
issue-comment is a skill published in the GitHub repository nearform/lastlight (39 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 535 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
project-setup
Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.
github-workflow
Install and operate a full GitHub issue-to-merge workflow for any repository using event-driven and cron missions. Handles issue planning, PR monitoring, CI fixing, staging review, and post-merge learning.
c-github
Interact with GitHub using the gh CLI and jq. Manage PRs, issues, repositories, and Actions workflows. Make raw API calls with gh api for anything not covered by built-in commands.
queue
A visible, editable Markdown work queue that agents drain autonomously — one task at a time or fanned out across parallel git worktrees — running each as a quick chore or the full feature-chain (design→prd→tdd→refine) with no user input. Use to queue, prioritize, stop/restart, seed from in-memory items, or…
fix
Fix a tracker issue end-to-end, or batch-queue all open GitHub issues from a repo.
open-source-playbook
Entry point and router for open-source work. Use when the user states an open-source goal without naming a specific task — "I want to open source this", "how do I grow this project", "make this repo look professional", "get more contributors", "prepare for v1.0" — or when a request touches several OSS concerns at…