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/nearform/lastlight/fixingnpx skills add nearform/lastlight --skill fixinggit 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/fixing)<a href="https://agentmods.dev/skills/nearform/lastlight/fixing"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/fixing.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 | $0.00046 | $0.03738 |
| Opus 5 | $0.00023 | $0.01869 |
| Sonnet 5 | $0.00009 | $0.00748 |
| Haiku 4.5 | $0.00005 | $0.00374 |
Grade A, and why
fixing 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 4d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixing
building is about implementing. This is about a failure that already
happened: find out why, decide whether it can be fixed here at all, and only
then repair it — minimally.
The discipline is diagnose-first. A blind second attempt on a PR whose tests need a database, or whose base branch is already red, spends a full install and test cycle to learn nothing. So you classify first and repair second.
The procedure
1. Read the real failure. Start from the structured CI report in your
prompt. When an excerpt is inconclusive, pull the full job log with
github_get_job_logs. When the harness could not download the logs at all your
prompt says so explicitly, and names the reason — say so in your verdict too,
and do not invent a cause from an annotation that was truncated.
The prNumber in your prompt is your target, and its head is already
checked out. Do not call github_list_pull_requests to "find" or "confirm"
it; you were handed it, and listing dumps every open PR for nothing.
2. Read the CI definition. .github/workflows/*.yml is already in the
checkout (the harness pre-cloned the PR head). Extract, per failing job: runner
OS, toolchain versions (setup-node, setup-python, matrix entries), the
exact commands, services:, env: and which secrets they reference, cache
config, and install flags (npm ci, --frozen-lockfile).
3. Name the differences between CI and this sandbox — explicitly. Toolchain
version (node -v against the workflow's), OS, absent services (postgres,
redis), absent secrets, no browser on the lean image, the egress allowlist. This
is the step that turns "the tests fail" into "the tests fail here because
CI runs Node 22 and this sandbox is on Node 20". Write the comparison down even
when it comes out empty — "no relevant difference" is itself a finding.
4. Reproduce. Run the exact failing command, aligned to CI's toolchain
where you can (fnm use <version> read from the workflow file). Install first
per the building skill.
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.
- 4d ago First seen · 282 lines · 46 tokens per session scan A dac877e7e63b
fixing is a skill published in the GitHub repository nearform/lastlight (22 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 3,738 once invoked, about $0.0002 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
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
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.
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
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…
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
brandkit
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional…