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 orchidautomation/pluxx --skill pluxx-build-installgit clone --depth 1 https://github.com/orchidautomation/pluxxWrote 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/orchidautomation/pluxx/pluxx-build-install)<a href="https://agentmods.dev/skills/orchidautomation/pluxx/pluxx-build-install"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-build-install/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/orchidautomation/pluxx/pluxx-build-install"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-build-install.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.00021 | $0.00322 |
| Opus 5.5 | $0.00008 | $0.00129 |
| Sonnet 5.5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
pluxx-build-install 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 2mo 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.
What it actually says
Pluxx Build Install
Use this skill when the user is ready to turn the current Pluxx source project into host-native bundles and test one or more targets locally.
Workflow
- Prefer
pluxx test --installwhen the user wants the strongest deterministic local proof in one command. - Otherwise, if the scaffold has changed materially, validate first:
pluxx doctorpluxx lintpluxx test
- Build the requested targets:
pluxx build- or
pluxx build --target <platforms...>
- Install only when the user wants local testing:
pluxx install --target <platforms...>- add
--trustwhen the plugin defines hook commands and the user has opted in
- If a host still looks wrong after install, use:
pluxx doctor --consumer <installed-path>
- Tell the user what was built and what was installed.
Rules
- Prefer target subsets when the user only cares about one host.
- Do not hide trust requirements for hook-enabled installs.
- Remind the user about host-specific reload steps when they matter.
- Never hand-edit
dist/; rebuild instead.
Output
- Say which targets were built.
- Say which targets were installed.
- Call out any remaining manual reload or trust steps.
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.
- 2mo ago First seen · 39 lines · 21 tokens per session scan A a2bc8e7ace3b
pluxx-build-install is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 322 once invoked, about $0.0001 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-09-03.
pluxx-build-install compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pluxx-build-installorchidautomation/pluxx | Skill | 5 | 1mo ago | MIT | A | 21 | Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |