Instructions for keeping Last Light’s code documentation and website documentation aligned in the same monorepo, a repository containing multiple related projects.

Use it before committing changes to listed Last Light server, workflow, configuration, connector, state, routing, package, or agent-context files, and when the documentation check requires an update.

Code changes can make documentation inaccurate, especially when documentation is stored in several locations or generated during a build.

How nearform/lastlight configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nearform/lastlight. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nearform/lastlight/main/.claude/skills/docs-sync/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/nearform/lastlight

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nearform/lastlight/docs-sync/github.svg)](https://agentmods.dev/skills/nearform/lastlight/docs-sync)

Your own site

<a href="https://agentmods.dev/skills/nearform/lastlight/docs-sync"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/docs-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nearform/lastlight/docs-sync"><img src="https://agentmods.dev/badge/skills/nearform/lastlight/docs-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,690 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

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 MCP Rug Pull · line 65
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00106	$0.02690
Opus 5.5	$0.00042	$0.01076
Sonnet 5.5	$0.00021	$0.00538
Haiku 4.5	$0.00011	$0.00269

Measured 1mo ago against content hash 976468e077ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-sync 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.

.claude/skills/docs-sync/SKILL.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

docs-sync

Last Light's documentation lives in two surfaces, and a code change can silently invalidate either. Since the monorepo migration both live in this repo (nearform/lastlight) — the www site is no longer a separate repo, so a doc update lands in the same commit as the code change:

In-repo spec — apps/server/spec/*.md. This is the rebuild-grade contract. It is the source of truth for the website's /spec/ section: apps/www/scripts/sync-spec.mjs copies these files into apps/www/src/content/spec/ at build time. So editing apps/server/spec/*.md is how you update the public spec — no separate edit under apps/www is needed for spec pages.
Hand-written site — apps/www/src/pages/docs/*.astro, apps/www/src/pages/*.astro, apps/www/src/data/docs-nav.ts, apps/www/src/pages/llms.txt.ts. These are not generated from anything. They drift the most.
The homepage — apps/www/src/pages/index.astro. Called out separately because it is the page nobody remembers to update and the one every visitor reads first. It makes countable, falsifiable claims (how many dashboard tabs, which sandbox backends, which skills exist) that go stale silently: an August 2026 audit found it still claiming "four tabs" against eleven, and two sandbox backends against five. It is marketing copy, so it does not list everything — but nothing on it may be wrong, and a genuinely new user-facing capability belongs there. Same rule for /comparisons/*, whose "what Last Light does that X doesn't" lists are claims about us.

The recurring failure mode: a workflow or skill is added and neither surface is updated. This skill exists to close that gap.

Counts are the tell. Any doc sentence containing a number that enumerates code ("four tabs", "two backends", "eleven workflows") is a liability. When you touch the thing being counted, grep the docs for the count and fix it — or better, reword it so it does not need a number.

Read the full file on GitHub · 150 lines

Changes

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 · +5 lines 976468e077ca
2mo ago First seen · 145 lines · 106 tokens per session scan A e40269fe414f

Subscribe to this mod's changes

docs-sync is a skill published in the GitHub repository nearform/lastlight (45 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 2,690 once invoked, about $0.0004 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.

Writing and docs agent ai coding harness

docs-sync next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
docs-syncnearform/lastlight	Skill	45	today	MIT	A	106	Claude Code
orcaVirtusLab/orca	Skill	198	16d ago	Apache-2.0	A	62	Claude Code
example-skillsammwyy/clay	Skill	24	2mo ago	none	A	37	Claude Code, Codex
open-code-reviewalibaba/open-code-review	Skill	50k	yesterday	Apache-2.0	A	98	Cursor
shapsynthetic-sciences/openscience	Skill	4.4k	yesterday	Apache-2.0	A	109	Claude Code, Codex
rowansynthetic-sciences/openscience	Skill	4.4k	yesterday	Apache-2.0	A	115	Claude Code, Codex
penguin-pluginPrism-Shadow/penguin-harness	Skill	3.2k	today	Apache-2.0	A	81	Claude Code, Codex

lastlight: Skill for Claude Code