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-prove-plugingit 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-prove-plugin)<a href="https://agentmods.dev/skills/orchidautomation/pluxx/pluxx-prove-plugin"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-prove-plugin/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-prove-plugin"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-prove-plugin.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.00023 | $0.00428 |
| Opus 5 | $0.00012 | $0.00214 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
pluxx-prove-plugin 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 8d 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 Prove Plugin
Use this skill when the user wants more than source confidence. This is the proof journey for a plugin that should be trusted in real hosts.
This workflow intentionally combines:
- deterministic validation
- build and install
- installed-state verification
- consumer diagnosis
- behavioral proof when workflow nuance matters
Workflow
- Start with deterministic trust:
pluxx doctorpluxx lintpluxx evalpluxx test
- Build the requested targets:
pluxx build- or
pluxx build --target <platforms...>
- If local proof matters, install:
pluxx install --target <platforms...>- add
--trustwhen hook-enabled installs require it
- Verify installed host state:
pluxx verify-install --target <platforms...>
- If the install still looks wrong, diagnose the consumer bundle:
pluxx doctor --consumer <installed-path>
- If workflow nuance matters, run behavioral proof:
pluxx test --install --trust --behavioral --target <platforms...>
- Return:
- what passed structurally
- what installed successfully
- what the host can actually see
- what the real behavior looked like
Rules
- Do not confuse build success with install success.
- Do not confuse install success with behavioral success.
- Findings come before reassurance.
- Prefer the guided proof path when the user wants a shareable or trustworthy result, not isolated green checks.
Output
- Return the proof state clearly:
- source health
- install health
- behavior health
- Explain the smallest sensible next step:
- reload
- trust hooks
- reinstall
- refine more
- or publish
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.
- 8d ago First seen · 62 lines · 23 tokens per session scan A 7a7e49a004ef
pluxx-prove-plugin is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 428 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.