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/eric-cielo/moflo/luminariumnpx skills add eric-cielo/moflo --skill luminariumgit clone --depth 1 https://github.com/eric-cielo/mofloWrote 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/eric-cielo/moflo/luminarium)<a href="https://agentmods.dev/skills/eric-cielo/moflo/luminarium"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/luminarium.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.1 | $0.00081 | $0.00760 |
| Opus 5 | $0.00041 | $0.00380 |
| Sonnet 5 | $0.00016 | $0.00152 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
luminarium 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/luminarium — Project Dashboard Link
Surface the URL for The Luminarium (the moflo daemon's localhost UI) for the project that this session is running in. No prompts, no confirmations — print the link and stop.
Procedure
-
Find the project root. Walk up from
process.cwd()looking for a.moflo/directory. The session's cwd is almost always the project root, so check there first. -
Read
.moflo/daemon.lock. It's a JSON file written by the daemon at bind time. The dashboard port is theportfield:{ "pid": 12345, "port": 33421, "startedAt": "...", ... }- If the file exists and
portis a valid number → the daemon is running and bound. Use that port. - If the file is missing or
portis absent/invalid → the daemon is not running. See step 4.
- If the file exists and
-
Print the link in a single line, with the path verbatim — Claude Code renders it as clickable:
The Luminarium: http://localhost:<port>Nothing else. No banner, no follow-up question, no "what would you like to do?".
-
If the daemon isn't running (no lock file, or unparseable), say so in one line and offer the start command — don't run it:
The moflo daemon isn't running for this project. Start it with: npx flo daemon start
Why read the lock, not compute the port
The port is project-deterministic (sha256(projectRoot) mapped into 33000–33999), but if the deterministic port was already taken at bind time the daemon scans forward and binds an alternate. The lock file is the only source of truth for what's actually bound. Do not compute the hash yourself — read the file.
Don't
- Don't fall back to any hardcoded port — there is no project-agnostic dashboard port; a literal would route to a foreign daemon on a multi-project machine. If the lock is missing, report "not running".
- Don't compute the deterministic port and report it as the link when the lock is missing — the daemon may be down, or bound to an alternate port. Report "not running" instead.
- Don't run
flo daemon startautomatically — the user asked for a link, not for daemon management. Leave starting to/healeror the user. - Don't open a browser. Print the URL; let the user click.
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.
- 5d ago First seen · 67 lines · 81 tokens per session scan A dd41d99cab46
luminarium is a skill published in the GitHub repository eric-cielo/moflo (18 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 760 once invoked, about $0.0004 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.