agentmods.dev

mcport: Instructions file for Codex

AGENTS.md

mcport AGENTS.md is an instructions file for Codex, OpenCode from sky32/mcport. It costs 1,831 tokens per session, scanned A, original, MIT.

Repository instructions for mcport, a local workspace runtime and Electron desktop application that provides tools for AI clients.

In plain words
What is it for?
Use them when modifying mcport's desktop shell, runtime, workspace handling, command execution, Git, authentication, SQLite state, tunnels, or project-specific guidance.
Why use it?
They explain the product structure and safety rules so changes do not cross workspace boundaries or weaken command, secret, runtime, or tunnel protections.

Instructions file for CodexOpenCode

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

This is sky32/mcport's own configuration. It tells Codex and OpenCode how to work on mcport 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 mcport configures →

not rated 6repo 4d ago A scan 1,831 tokens original MIT
View source ↗ sky32/mcport
Reuse

Borrowing it

Nothing to install: this file belongs to sky32/mcport. 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/sky32/mcport/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/sky32/mcport

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sky32/mcport/agents-md"><img src="https://agentmods.dev/badge/instructions/sky32/mcport/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,831 This file is loaded in full into every session.
When invoked 1,831 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.01831 $0.01831
Opus 5.5 $0.00732 $0.00732
Sonnet 5.5 $0.00366 $0.00366
Haiku 4.5 $0.00183 $0.00183

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

Security

Grade A, and why

mcport 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 · 172 lines

How it starts

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

MCPort — Agent Guide

This repository implements a generic local Workspace MCP Runtime plus an Electron Desktop shell.

Product model

  • Desktop owns Workspace registration, Runtime lifecycle (Electron utilityProcess), Tunnel lifecycle, managed tunnel binaries (cloudflared/frpc), proxy settings, secure secrets, tray/login integration, health checks, and UI.
  • Runtime owns MCP transport, tools, Workspace safety, command execution, Git, project history, authentication, and SQLite runtime state.
  • AI clients own reasoning and project-specific knowledge.
  • Project-specific instructions and Skills live in target Workspaces, not in this server.

Invariants

  1. Runtime executes as the local OS user.
  2. File and cwd operations remain inside the selected Workspace after realpath/symlink validation.
  3. Commands use executable + args[] with shell: false.
  4. Executables are plain command names (no / or \) and must pass Allowed Commands with exact-name matching.
  5. The command allowlist is not an OS sandbox; child processes inherit the Runtime user's permissions.
  6. Single-Workspace MCP endpoints may infer Workspace; ambiguous multi-Workspace endpoints require an explicit Workspace.
  7. Desktop automatically manages Runtime startup and recovery; users control Tunnel exposure, not Runtime lifecycle.
  8. Public Workspaces share one hostname and route by /w/<workspace>/... on the default listener's non-loopback Host path.
  9. Public authentication is per Workspace: built-in OAuth or Bearer Token. There is no unauthenticated public access.
  10. Built-in OAuth uses oidc-provider; application code supplies Workspace policy, interaction UI, persistence adapter, and MCP resource binding.
  11. Runtime configuration belongs in SQLite; Desktop routing/preferences belong in Desktop settings; secrets use safeStorage.
  12. Tool tiers (readonly/standard/full) are part of the public MCP API and must stay internally consistent with tools/list and src/tool-tier-smoke.ts.
  13. Project history is model-mediated; Desktop never records chat text in the background.

Read the full file on GitHub · 172 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.

  1. 2mo ago First seen · 172 lines · 1,831 tokens per session scan A 8fe51855cac4

Subscribe to this mod's changes

mcport AGENTS.md is an instructions file published in the GitHub repository sky32/mcport (6 stars, last pushed 4d ago), licensed MIT. It adds 1,831 tokens to every session, about $0.0073 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

mcport AGENTS.md compared with instructions from other repositories

mcport AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mcport AGENTS.mdsky32/mcportInstructions file64d agoMITA1,831Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,649GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode ai-customization.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA1,907GitHub Copilot