Borrowing it
Nothing to install: this file belongs to arch3rPro/1Panel-Appstore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/arch3rPro/1Panel-Appstore/main/AGENTS.mdgit clone --depth 1 https://github.com/arch3rPro/1Panel-AppstoreWrote 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/arch3rpro/1panel-appstore/agents-md)<a href="https://agentmods.dev/instructions/arch3rpro/1panel-appstore/agents-md"><img src="https://agentmods.dev/badge/instructions/arch3rpro/1panel-appstore/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.
<a href="https://agentmods.dev/instructions/arch3rpro/1panel-appstore/agents-md"><img src="https://agentmods.dev/badge/instructions/arch3rpro/1panel-appstore/agents-md.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.00821 | $0.00821 |
| Opus 5.5 | $0.00328 | $0.00328 |
| Sonnet 5.5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
1Panel-Appstore 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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Shape
This repository is a third-party 1Panel local app store. It is mostly YAML, Docker Compose files, READMEs, icons, and helper shell scripts. There is no central application build step.
Top-level files:
data.yaml: app store metadata and category/tag definitions.apps/<app-key>/: one app package per directory.skills/: app-generation guidance, templates, and helper scripts.update/: update-detection and README-version sync scripts.
App Package Layout
Use this structure for each app:
apps/<app-key>/
├── data.yml
├── logo.png
├── README.md
├── README_en.md
└── <version>/
├── data.yml
├── docker-compose.yml
└── data/
Some apps also include latest/. When both latest/ and a concrete version
exist, latest/ should use an image tagged latest, and the concrete version
directory should use the pinned image tag.
1Panel Conventions
- App keys are lowercase and hyphenated, and must match the app directory name.
- Top-level
apps/<app-key>/data.ymlcontains display metadata. - Version-level
data.ymlcontainsadditionalProperties.formFields. - Prefer standard port variables such as
PANEL_APP_PORT_HTTP,PANEL_APP_PORT_HTTPS,PANEL_APP_PORT_API,PANEL_APP_PORT_ADMIN,PANEL_APP_PORT_PROXY,PANEL_APP_PORT_DB,PANEL_APP_PORT_SSH,PANEL_APP_PORT_S3, andPANEL_APP_PORT_SYNC. - Each
PANEL_APP_PORT_*used indocker-compose.ymlshould have a matching form field in the versiondata.yml. - Compose services should use
container_name: ${CONTAINER_NAME},restart: always, the external1panel-network, relative./data/volume paths for persistence, andlabels: createdBy: "Apps". - Use
./data/...mounts instead of host absolute paths unless the app genuinely requires host integration. - Keep app metadata tags aligned with
data.yaml.
App Creation Workflow
Before adding or changing app packages, read skills/SKILL.md. It documents
the expected 1Panel packaging workflow, metadata fields, compose conversion
rules, README shape, and icon lookup order.
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.
- 1mo ago First seen · 100 lines · 821 tokens per session scan A 9b255609bb40
1Panel-Appstore AGENTS.md is an instructions file published in the GitHub repository arch3rPro/1Panel-Appstore (221 stars, last pushed today), licensed MIT. It adds 821 tokens to every session, about $0.0033 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.