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 BlackBeltTechnology/pi-agent-dashboard --skill lightcraftgit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/lightcraft)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/lightcraft"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/lightcraft/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/blackbelttechnology/pi-agent-dashboard/lightcraft"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/lightcraft.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00091 | $0.02061 |
| Opus 5.5 | $0.00036 | $0.00824 |
| Sonnet 5.5 | $0.00018 | $0.00412 |
| Haiku 4.5 | $0.00009 | $0.00206 |
Grade A, and why
lightcraft 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 yesterday.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LightCraft — headless photo development
LightCraft is ArtCraft's RAW developer: non-destructive develop sliders plus an export encoder. pi-craft
provisions the headless lightcraft-cli on first use (no desktop app). Choosing between apps, the
discover → execute → save → verify loop and the MCP policy live in craft-studio.
What it is for / formats
Develops one photo → one exported file. Reads camera RAW (DNG, ARW, NEF, RAF…) and also plain png jpg tif
(verified with png and with DNGs from synth-merge; no real camera RAW was available here — use ffmpeg-made
images or synth-merge to try things). Exports jpg png tif webp avif jxl psd dng
(chosen by the -o extension). Edits live in a LightCraft library, not in a project file. Pixel editing
(layers, masks, compositing) is PhotoCraft; vector art is VectorCraft.
CLI dialect
pi-craft lightcraft exec <args…> passes the arguments to lightcraft-cli verbatim.
There is no describe and no --cmd flag — the dialect has two routes:
lightcraft-cli render <IN> -o <OUT> [--set CONTROL=VALUE]… [--settings F.json] [--preset ID] [--size N] [--quality Q] [--opt KEY=VALUE]…
lightcraft-cli run [--import PATH]… | [--demo] | [--library DIR] <command> [key=value | '{json}']… [<command> …]…
lightcraft-cli commands [--json] # every command id + params (626 lines)
lightcraft-cli controls [--json] # every develop slider id + range/default (122)
lightcraft-cli merge hdr|panorama|hdr-panorama [--preview OUT.png] FILES… # writes <first>-HDR.dng next to the inputs
lightcraft-cli synth-merge hdr|panorama -o DIR # synthetic DNG brackets / overlapping PNGs
renderis the one-shot route: develop one file, export it.--setis repeatable;--size Nis the long edge (default full size);--quality1–100 (default 92) for jpg/avif/jxl;--optpasses anyapp.exportoption (--opt colorSpace=displayP3,--opt bitDepth=16,--opt shortEdge=1080).runis the command route: a word without=starts the next command;key=valueare its parameters (JSON when parsable). It prints one JSON line per command and exits non-zero on failure. Chaindevelop.set control=<id> value=<n>,develop.auto, thenapp.export path=<abs> longEdge=<n>.- Presets are applied with
--preset ID(ids fromrun --demo presets.list, e.g.lc.bw-high-contrast,lc.warm-glow,lc.teal-orange) or thepreset.applycommand.--settings F.jsonmerges a partial settings object whose shape isdevelop.getoutput ({"light":{"exposure":1.5}}).
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.
- yesterday First seen · 121 lines · 91 tokens per session scan A 1eef476a19ec
lightcraft is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (319 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 2,061 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-10-15.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-plan-by-design
Compile a design document into a ralphex execution plan.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-project
Understand the current project before defining a product change that must fit into an existing product.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.