pluxx-rewrite-instructions

pluxx-rewrite-instructions is a skill for Codex from orchidautomation/pluxx. It costs 22 tokens per session (282 once invoked), scanned A, original, MIT.

A workflow for rewriting the shared instructions file in a Pluxx plugin so it explains the actual product and how to use it. It changes only the generated section of INSTRUCTIONS.md.

In plain words
What is it for?
Use it to prepare product context, rewrite plugin instructions, and check the result with Pluxx lint and tests.
Why use it?
It replaces generic guidance with concise, product-specific instructions and makes setup, authentication, account, and runtime boundaries clearer.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to prepare product context, rewrite plugin instructions, and check the result with Pluxx lint and tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orchidautomation/pluxx/pluxx-rewrite-instructions
Install

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.

Any agent
npx skills add orchidautomation/pluxx --skill pluxx-rewrite-instructions
Clone the repo
git clone --depth 1 https://github.com/orchidautomation/pluxx

Made for: Codex.

Wrote 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.

agentmods badge for pluxx-rewrite-instructions

README.md
[![agentmods](https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-rewrite-instructions/github.svg)](https://agentmods.dev/skills/orchidautomation/pluxx/pluxx-rewrite-instructions)
Your own site
<a href="https://agentmods.dev/skills/orchidautomation/pluxx/pluxx-rewrite-instructions"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-rewrite-instructions/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.

agentmods 80×15 button for pluxx-rewrite-instructions

Your own site · 80×15
<a href="https://agentmods.dev/skills/orchidautomation/pluxx/pluxx-rewrite-instructions"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/pluxx-rewrite-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 282 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00282
Opus 5 $0.00011 $0.00141
Sonnet 5 $0.00004 $0.00056
Haiku 4.5 $0.00002 $0.00028

Measured 8d ago against content hash be07973702ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

pluxx-rewrite-instructions 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.

example/pluxx/skills/pluxx-rewrite-instructions/SKILL.md · 36 lines

What it actually says

Pluxx Rewrite Instructions

Use this skill when the scaffold structure is fine but the shared instructions need to sound more like the actual MCP product.

Workflow

  1. Refresh context:
    • pluxx agent prepare
    • include --website, --docs, and local context files when they clarify the product
  2. Generate or run the instructions prompt:
    • pluxx agent prompt instructions
    • or pluxx agent run instructions --runner codex
  3. Limit edits to the generated block in INSTRUCTIONS.md.
  4. Re-run:
    • pluxx lint
    • pluxx test

Rules

  • Keep the output concise and operational.
  • Make setup/auth caveats explicit when they affect tool usage.
  • Use branded product-facing language and avoid raw MCP server/tool naming unless technically required.
  • Clarify setup/admin/account/runtime boundaries so agents know where each skill belongs.
  • Explain what the plugin is for, how the skills should be used, and what the host agent must not do.
  • Do not rewrite custom sections unless the user explicitly asks.

Output

  • Summarize the instruction changes.
  • Mention any setup/auth caveats that still need manual confirmation.
Files

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.

Changes

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.

  1. 8d ago First seen · 36 lines · 22 tokens per session scan A be07973702ec

Subscribe to this mod's changes

pluxx-rewrite-instructions is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 282 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens