pluxx: Instructions file for Codex

AGENTS.md

pluxx AGENTS.md is an instructions file for Codex, OpenCode from orchidautomation/pluxx. It costs 504 tokens per session, scanned A, original, MIT.

Project instructions for pluxx, including which planning documents to read and how documentation relates to Linear, a tool for tracking work and project status.

In plain words
What is it for?
Use them when changing project plans, documentation, shipped features, compatibility information, or release-readiness records.
Why use it?
They help keep product details, release status, priorities, and documentation consistent when changes are made.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is orchidautomation/pluxx's own configuration. It tells Codex and OpenCode how to work on pluxx itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pluxx configures →

Reuse

Borrowing it

Nothing to install: this file belongs to orchidautomation/pluxx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/orchidautomation/pluxx/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/orchidautomation/pluxx

Made for: Codex, OpenCode.

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 AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/orchidautomation/pluxx/agents-md"><img src="https://agentmods.dev/badge/instructions/orchidautomation/pluxx/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 504 This file is loaded in full into every session.
When invoked 504 The same file — it is already loaded in full.
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.00504 $0.00504
Opus 5.5 $0.00202 $0.00202
Sonnet 5.5 $0.00101 $0.00101
Haiku 4.5 $0.00050 $0.00050

Measured 2mo ago against content hash 0d65c784e14b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pluxx AGENTS.md 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.

AGENTS.md · 71 lines

What it actually says

AGENTS

Start Here

If you are new to the repo, read these first:

  1. docs/start-here.md
  2. docs/todo/queue.md
  3. docs/todo/master-backlog.md
  4. docs/roadmap.md

Use Linear for ticket-level detail and execution state.

Docs Maintenance Rule

When editing a doc that contains a Doc Links block:

  1. read the files listed under Related
  2. update any files listed under Update together if the change affects them
  3. keep the high-level story aligned across:
    • one maintained plugin source
    • four native destinations
    • OSS authoring substrate first
    • later trust / distribution layer second

Docs And Linear Sync Rule

If a change affects any of these:

  • product truth
  • what is shipped vs not shipped
  • proof state
  • priority order
  • host compatibility or lifecycle truth
  • release readiness

then update the relevant repo docs and the relevant Linear issue or project in the same work block.

Minimum repo-doc surfaces to consider:

If the change is narrower than that, update only the specific source-of-truth doc it affects.

Canonical Planning Files

The canonical planning docs now live in docs/todo/:

Legacy compatibility shims remain at:

Edit the canonical files, not the shims.

Public vs Private Material

Keep public repo docs focused on product, proof, and execution.

Do not store account-specific GTM notes, named prospect research, or private outreach planning in the public repo.

Orchid Routing

  • Linear team: PLUXX
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. 2mo ago Changed · +4 lines · +12 tokens per session 0d65c784e14b
  2. 2mo ago First seen · 67 lines · 492 tokens per session scan A b82aab8d6ad7

Subscribe to this mod's changes

pluxx AGENTS.md is an instructions file published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 1mo ago), licensed MIT. It adds 504 tokens to every session, about $0.0020 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-08-31.

Related

pluxx AGENTS.md compared with instructions from other repositories

pluxx AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pluxx AGENTS.mdorchidautomation/pluxxInstructions file51mo agoMITA504Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode