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 buildinggit 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/building)<a href="https://agentmods.dev/skills/nearform/lastlight/building"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/building/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/building"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/building.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 37 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00052 | $0.01819 |
| Opus 5.5 | $0.00021 | $0.00728 |
| Sonnet 5.5 | $0.00010 | $0.00364 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
building 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building
How to install, build, test, and gate a change in the sandbox. The same discipline whether you're implementing a feature, fixing review feedback, or verifying someone else's PR.
Workspace & git
The harness pre-cloned the repo; your cwd is the repo root (or a <repo>/
subdirectory — check with ls -la). Git is configured for clone/fetch/pull and
local commits. If auth fails after ~1 hour, call the github_refresh_git_auth
MCP tool. Suppress noise where it helps: git clone --quiet, CI=true.
Getting work onto the branch is not a git operation: a commit built by git here
is unsigned and a repo that requires signed commits blocks it permanently, so a
phase that publishes does it with github_publish rather than git push. Your
prompt says whether yours publishes and with what arguments.
A new file cannot be published executable. GitHub builds the commit from
paths and contents, with no file mode, so a new 100755 file is refused and
nothing is published. Adding a script is the case you will hit: leave it
non-executable (no chmod +x) and invoke it through its interpreter —
bash scripts/verify.sh, python scripts/check.py — in the docs, the CI
workflow and anywhere else that calls it. Symlinks, submodule pointers and a
mode change on an existing file are refused too, and those need a human.
Install-first
node_modules (and any other dependency dir) is always absent on arrival —
by design, not a blocker. Installing is the first step, not a reason to skip
verification. Detect the package manager from the lockfile and use the
frozen/CI variant:
package-lock.json→npm cipnpm-lock.yaml→corepack pnpm install --frozen-lockfileyarn.lock→corepack yarn install --frozen-lockfile
Node is available via fnm + corepack; the egress allowlist permits the public
package registries, so install works. For a monorepo, install at the root, then
operate on the changed package. For non-Node repos, use the ecosystem's
equivalent (pip install, cargo build, go mod download, …) read from the
project's manifest.
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 Changed · +7 lines c5f94c12f51f
- 2mo ago First seen · 136 lines · 52 tokens per session scan A a37005811d8f
building is a skill published in the GitHub repository nearform/lastlight (41 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 1,819 once invoked, about $0.0002 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
orca
Use when the user asks to run an Orca flow (e.g. "use orca to implement …"), or when delegating a well-defined implementation task to Orca's autonomous multi-agent flow — a headless plan-code-review CLI to hand a coding task to instead of implementing it yourself.
coding
Use when five specialized coding agents (linter, perf, refactor, security, test) that enforce quality gates across the development lifecycle. From lint enforcement through performance profiling, refactoring, security auditing, and test coverage. Use when working with coding agents.
test-agent
Use when writing comprehensive test suites covering happy paths, error paths, edge cases, and integration points.
example-skill
Counts lines, words, and bytes in a text file using the bundled count.sh script. Use when asked to count/measure a file's size in these terms.
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
shap
Model interpretability and explainability using SHAP (SHapley Additive exPlanations). Use this skill when explaining machine learning model predictions, computing feature importance, generating SHAP plots (waterfall, beeswarm, bar, scatter, force, heatmap), debugging models, analyzing model bias or fairness, comparing…