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 agentrhq/agent-automation-skills --skill luma-guest-selectiongit clone --depth 1 https://github.com/agentrhq/agent-automation-skillsWrote 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/agentrhq/agent-automation-skills/luma-guest-selection)<a href="https://agentmods.dev/skills/agentrhq/agent-automation-skills/luma-guest-selection"><img src="https://agentmods.dev/badge/skills/agentrhq/agent-automation-skills/luma-guest-selection/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/agentrhq/agent-automation-skills/luma-guest-selection"><img src="https://agentmods.dev/badge/skills/agentrhq/agent-automation-skills/luma-guest-selection.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.00046 | $0.01185 |
| Opus 5 | $0.00023 | $0.00593 |
| Sonnet 5 | $0.00009 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade C, and why
luma-guest-selection scanned grade C with 1 finding 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 11d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
Approve only pending guests who clearly satisfy the host's confirmed rubric. For every non-match, missing field, contradiction, unavailable profile, or uncertain identity, leave the guest unchanged. Never decline a guest How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Luma Guest Selection
Core contract
Approve only pending guests who clearly satisfy the host's confirmed rubric. For every non-match, missing field, contradiction, unavailable profile, or uncertain identity, leave the guest unchanged. Never decline a guest.
Prerequisites
This skill uses the official Luma commands provided by Webcmd.
- Run
node --version; Node.js 20 or newer is required. - Run
webcmd --version. If Webcmd is missing, ask before installing it globally withnpm install -g @agentrhq/webcmd. - When the agent runtime supports Webcmd skills, refresh them with
webcmd skills install --provider codexand loadwebcmd:webcmd-usagebefore live Webcmd work. Otherwise use live--helpoutput. - Run
webcmd luma --helpto verify that the Luma commands are installed. If they are unavailable, follow thewebcmd:webcmd-usagediscovery order: check a complete Luma-filteredwebcmd list -f jsonresult, then, only if it is empty, runwebcmd plugin search luma -f json. If a matching plugin is available, ask before installing its returnedinstallSourcewithwebcmd plugin install <installSource>, then rerunwebcmd luma --help. If discovery fails or returns no match, stop and report it. - Run
webcmd doctor, thenwebcmd luma whoami -f json. If authentication is required, runwebcmd luma login, follow its human handoff, and rerunwhoamibefore continuing.
Workflow
- List managed events with
webcmd luma events -f jsonand have the host select the event. - Fetch the complete current
pending_approvalguest set withwebcmd luma guests <eventId> --status pending_approval --limit <N> -f json. Stop on pagination, authentication, or shape errors; never evaluate a partial list. - Inspect standard fields,
profiles, and arbitraryanswers. Tell the host which evidence fields exist, then ask for approval criteria once. If criteria were already supplied, do not ask again. - Convert the request into required conditions, acceptable evidence, and missing-data handling.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 87 lines · 46 tokens per session scan C 428633bc1913
luma-guest-selection is a skill published in the GitHub repository agentrhq/agent-automation-skills (2 stars, last pushed 23d ago), licensed MIT. It adds 46 tokens to every session and 1,185 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.