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 agentmods add instructions/mooqii/openpanels/agents-mdgit clone --depth 1 https://github.com/mooqii/OpenPanelsWrote 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/instructions/mooqii/openpanels/agents-md)<a href="https://agentmods.dev/instructions/mooqii/openpanels/agents-md"><img src="https://agentmods.dev/badge/instructions/mooqii/openpanels/agents-md.svg" alt="Measured on agentmods" 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 | $0.00896 | $0.00896 |
| Opus 5 | $0.00448 | $0.00448 |
| Sonnet 5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
OpenPanels 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MyOpenPanels Repository Agent Notes
Engineering
- Use independent professional judgment during solution discussions. Treat the user's proposed approach as input, recommend a better alternative when one exists, and follow their approach as a requirement only when explicitly asked.
- Build frontend pages with HeroUI's native components wherever possible. Create custom components only when HeroUI primitives or their composition cannot meet the product requirements.
Local CLI and Studio
- Prefer the checkout-local CLI wrapper. Set
MYOPENPANELS_CLI="$PWD/scripts/myopenpanels-dev"when it is executable; otherwise usemyopenpanelsfromPATH. - For a request that only opens MyOpenPanels, do not inspect or broadly search the
repository and do not run Agent Bootstrap. Start Studio directly:
MYOPENPANELS_CLI="$PWD/scripts/myopenpanels-dev" scripts/myopenpanels-dev studio start --local-only --project-dir "$PWD" --format json. Followdata.nextRequiredActionby opening its URL unchanged with an in-app browser. Only if that is unavailable or fails, executedata.nextRequiredAction.fallback.argvwith the resolved CLI. Do not execute the compatibility display command or report completion before an opener succeeds. If start fails or reports a stale server, run:MYOPENPANELS_CLI="$PWD/scripts/myopenpanels-dev" scripts/myopenpanels-dev studio serve --project-dir "$PWD" --local-only --format json. - For Wiki, Canvas, or task work after Studio is running, call
scripts/myopenpanels-dev agent bootstrap --format json, then execute only its returned actionargvarrays with the resolved CLI. - Canvas, panel, Wiki, and task commands automatically target the current visible
Project. Do not pass context, session, or panel IDs unless debugging CLI
internals. Create a Project with
scripts/myopenpanels-dev project createonly when the user explicitly asks. - After changing the CLI, server, Studio UI, or embedded assets, rebuild with
scripts/myopenpanels-dev, stop any running development Studio, and restart it before browser verification. Runcorepack pnpm --dir apps/studio buildfirst when UI assets changed. Treat"data.reusedExisting": trueafter such changes as stale: runscripts/myopenpanels-dev studio stop --project-dir "$PWD" --format json, then rebuild and start Studio again.
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.
- 3d ago First seen · 68 lines · 896 tokens per session scan A d2b03eae012d
OpenPanels AGENTS.md is an instructions file published in the GitHub repository mooqii/OpenPanels (8 stars, last pushed 1mo ago), licensed MIT. It adds 896 tokens to every session, about $0.0045 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-08-31.
Other instructions, from other repositories
deer-flow copilot-instructions.md
Copilot instructions for bytedance/deer-flow, covering copilot onboarding instructions for deerflow, 1) repository summary, 2) runtime and toolchain requirements, 3) build/test/lint/run - verified command sequences and a. bootstrap and install.
LeAgent AGENTS.md
Instructions for vixues/LeAgent, covering leagent development guidelines, project overview, architecture, execution topology (one kernel, many ingresses) and surface map (where things live).
sprawling CLAUDE.md
Instructions for 2youg1/sprawling: See AGENTS.md. It is the whole instruction set for this repository — the loop, what to read first, the five steps of one change, the rules a machine holds, and the language and commit conventions.
codex-acp-bridge AGENTS.md
Instructions for normahq/codex-acp-bridge, covering codex-acp-bridge — agents.md, development standards, quality gates (required), logging policy and bridge guardrails.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
vant AGENTS.md
Instructions for dhaupin/vant, covering agents.md — vant agent guide, what is vant?, your job, brain router interface and middleware chain.