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-translate-hostsgit 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-translate-hosts)<a href="https://agentmods.dev/skills/orchidautomation/pluxx/pluxx-translate-hosts"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-translate-hosts/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-translate-hosts"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-translate-hosts.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.00031 | $0.00371 |
| Opus 5 | $0.00015 | $0.00186 |
| Sonnet 5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
pluxx-translate-hosts 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 Translate Hosts
Use this skill when the user needs to understand how a Pluxx source project maps into the core four.
The goal is not to promise fake parity. The goal is to preserve author intent and explain where each host gets a native surface, a translated equivalent, a weaker equivalent, or no honest equivalent.
Workflow
- Run or inspect current validation output:
pluxx lintpluxx build --target claude-code cursor codex opencode
- Review the highest-risk surface:
- commands and argument UX
- specialist agents/subagents
- hooks and trust behavior
- permissions and tool approval intent
- MCP, auth, and runtime materialization
- Explain the mapping by bucket:
- instructions
- skills
- commands
- agents
- hooks
- permissions
- runtime
- distribution
- For every important caveat, classify it as:
- preserve
- translate
- degrade
- drop
- Recommend the best source-shape fix when a degraded host could be improved by moving intent to commands, agents, permissions, hooks, or runtime config.
Rules
- Do not flatten host-specific nuance into “supported everywhere.”
- Do not hand-edit generated
dist/as the fix; fix the source project. - Prefer improving source authoring shape over adding target-specific hacks.
Output
- concise preserve/translate/degrade/drop matrix
- highest-value source-shape fix
- target-specific caveats users need to know before publishing
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 · 50 lines · 31 tokens per session scan A ec2ca1b201af
pluxx-translate-hosts is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 371 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…