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/debug-productionnpx skills add nearform/lastlight --skill debug-productiongit 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/debug-production)<a href="https://agentmods.dev/skills/nearform/lastlight/debug-production"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/debug-production.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.00066 | $0.01023 |
| Opus 5 | $0.00033 | $0.00511 |
| Sonnet 5 | $0.00013 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
debug-production 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug a Last Light instance via the CLI
Read a running instance's state over its admin API with the lastlight CLI —
no SSH, no poking SQLite or jsonl files on the box. Every command takes
--json for machine-parseable output; prefer it when you need to extract
fields.
0. Connect
The CLI talks to whatever instance you logged into (saved in
~/.lastlight/config.json). Confirm you're pointed at the right one and the
token is valid:
lastlight status # instance URL, server health, token validity
If the token is missing/expired, authenticate (the prod instance URL lives in local agent memory — see the "Last Light production server" note):
lastlight login https://<instance> # browser handoff (password/Slack/GitHub)
lastlight login https://<instance> --password # headless fallback
For one-off targeting without saving, pass --url / --token on any command,
or set LASTLIGHT_URL / LASTLIGHT_TOKEN (env wins over the saved config).
1. Find the broken run
lastlight workflow list --status failed # recent failures
lastlight workflow list --status active # running + paused now
lastlight workflow list --workflow pr-review --limit 50
Copy the run ID from the table.
2. Inspect the run's phases
lastlight workflow log <run-id> # run header + per-phase table (✓/✗, duration, session id, error)
lastlight workflow log <run-id> --follow # then tail the current phase live
The phase table shows which phase failed, its error snippet, and the SESSION
id you need for the transcript.
3. Read / tail the agent transcript
lastlight session list # recent sandbox sessions (TYPE, MODEL, LIVE)
lastlight session log <session-id> # full transcript
lastlight session log <session-id> --follow # live tail (SSE) of an in-flight phase
4. Search across runs
lastlight logs search "ECONNREFUSED" # errors ledger (default)
lastlight logs search "rate limit" --scope all # errors + transcript content
lastlight logs search "could not clone" --scope messages --limit 20
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 · 109 lines · 66 tokens per session scan A 7e56a2c9a8e8
debug-production is a skill published in the GitHub repository nearform/lastlight (22 stars, last pushed 7d ago), licensed MIT. It adds 66 tokens to every session and 1,023 once invoked, about $0.0003 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
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…
minimalist-ui
Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.