What is opuspad AGENTS.md?

A repository guide for Opuspad, a planned Chrome extension for editing Markdown files. It describes the design-first workflow and the intended React, TypeScript, and Vite structure.

Use it when implementing the extension scaffold, organizing its source files, or checking work against the design specification.

The application scaffold and build scripts are not yet committed, so the guide identifies the design documents and verification steps to follow.

How luanjunyi/opuspad configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to luanjunyi/opuspad. 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/luanjunyi/opuspad/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/luanjunyi/opuspad

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/luanjunyi/opuspad/agents-md/github.svg)](https://agentmods.dev/instructions/luanjunyi/opuspad/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/luanjunyi/opuspad/agents-md"><img src="https://agentmods.dev/badge/instructions/luanjunyi/opuspad/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/luanjunyi/opuspad/agents-md"><img src="https://agentmods.dev/badge/instructions/luanjunyi/opuspad/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 563 This file is loaded in full into every session.

When invoked 563 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.

Model	Per session	Once invoked
Fable 5.1	$0.00563	$0.00563
Opus 5.5	$0.00225	$0.00225
Sonnet 5.5	$0.00113	$0.00113
Haiku 4.5	$0.00056	$0.00056

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

Security

Grade A, and why

opuspad 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 · 34 lines

How it starts

The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

This repository is currently spec-first. Start with .spec/design-doc-md-editor-chrome.md for architecture, task scope, and manual verification steps. Use .spec/tracker.md to track task status and .spec/escalations.md for blockers that need a decision. The application scaffold has not been committed yet; when Task 1 lands, keep runtime code in src/, shared file-system logic in src/services/, UI pieces in src/components/, and treat dist/ as generated build output.

Build, Test, and Development Commands

There are no checked-in build scripts yet because the extension scaffold is still pending. Once Task 1 is implemented, standard commands should be:

npm install: install Vite, React, and extension dependencies.
npm run dev: start the local development server for UI work.
npm run build: create the unpacked Chrome extension bundle in dist/.

Until those scripts exist, use the verification steps in .spec/design-doc-md-editor-chrome.md as the executable source of truth.

Coding Style & Naming Conventions

The design doc targets React 18, TypeScript 5, Vite 5, Manifest V3, CodeMirror, and BlockNote. Follow a simple layout: 2-space indentation, PascalCase for React components (MarkdownEditor.tsx), camelCase for functions and hooks (mountWorkspace), and kebab-case only for non-code asset names when needed. Keep file-system access code isolated from UI code, and prefer small modules over large mixed-purpose files.

Testing Guidelines

No automated test framework is committed yet. For now, every change must pass the manual checks in the design doc, especially Chrome extension loading, workspace mounting, and debounced file saves. When tests are added, prefer *.test.ts and *.test.tsx files near the code they cover or under tests/, and focus first on src/services/fileSystem.ts, editor routing, and save behavior.

Commit & Pull Request Guidelines

This repository has no established commit history yet, so set the baseline now: use short imperative commit subjects such as Add extension scaffold or Implement file tree sidebar. Keep each commit focused on one task from .spec/tracker.md. Pull requests should name the task addressed, summarize behavior changes, list verification steps performed, and include screenshots or a short video for UI changes.

Read the full file on GitHub · 34 lines

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.

2mo ago First seen · 34 lines · 563 tokens per session scan A 18083229ff3b

Subscribe to this mod's changes

opuspad AGENTS.md is an instructions file published in the GitHub repository luanjunyi/opuspad (2 stars, last pushed 5mo ago), licensed ISC. It adds 563 tokens to every session, about $0.0023 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.

Frontend React ai-ready chrome-extension local-first markdown wysiwyg

opuspad AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
opuspad AGENTS.mdluanjunyi/opuspad	Instructions file	2	5mo ago	ISC	A	563	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

opuspad: Instructions file for Codex