Remarc AGENTS.md

A development guide for Remarc, a macOS menu-bar app built with SwiftUI and AppKit that lets users comment on selected text.

In plain words
What is it for?
Use it when changing the app, especially its interface, then building, relaunching, debugging, or locating stored comments.
Why use it?
It records the app's build settings, data locations, logging behavior, and relaunch requirements so changes can be built and checked consistently.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/metedata/remarc/agents-md
Clone the repo
git clone --depth 1 https://github.com/metedata/Remarc

Made for: Codex, OpenCode.

Per session 1,160 This file is loaded in full into every session.
When invoked 1,160 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
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 $0.01160 $0.01160
Opus 5 $0.00580 $0.00580
Sonnet 5 $0.00232 $0.00232
Haiku 4.5 $0.00116 $0.00116

Measured 3d ago against content hash 99f862718643, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

Remarc AGENTS.md scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf app/DerivedData
AGENTS.md · 76 lines

How it starts

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

Remarc

macOS menu bar app (SwiftUI + AppKit) for contextual commenting on text selections.

  • Bundle ID: com.metepolat.Remarc
  • Min macOS: 14.0 (MACOSX_DEPLOYMENT_TARGET in app/Config/Shared.xcconfig is the source of truth), Swift 6.0+, LSUIElement (no dock icon)
  • Build: cd app && xcodebuild build -workspace Remarc.xcworkspace -scheme Remarc -configuration Debug -derivedDataPath "$(pwd)/DerivedData"
  • Debug log: /tmp/remarc_debug.log (Debug builds only; release builds write no log file unless defaults write com.metepolat.Remarc debugFileLoggingEnabled -bool YES)
  • Data: ~/Library/Application Support/Remarc/comments.json (legacy fallback: data.json)

MANDATORY: After every successful build, you MUST relaunch Remarc. The user cannot verify changes otherwise. Do this every single time, no exceptions:

  1. Build with -derivedDataPath "$(pwd)/DerivedData" (deterministic output path — no grep/find needed)
  2. Relaunch: pkill -x Remarc; sleep 0.5; open app/DerivedData/Build/Products/Debug/Remarc.app

Build

When working on UI changes in SwiftUI, always do a clean build after layout changes to avoid stale build cache issues. Use xcodebuild clean or delete DerivedData when builds behave unexpectedly.

Worktree Builds

When building from worktrees, always verify the correct DerivedData path and binary location before launching. Use absolute paths instead of $PWD in build commands.

UI Work

When the user describes a UI bug, confirm WHICH specific component/view they mean before editing. Ask clarifying questions if the target is ambiguous (e.g., 'comment cards' vs 'session chips').

Development

Contribution Attribution

Use Mete Polat <[email protected]> as the author of repository and automated release commits and as the tagger of annotated tags. Automated commits must use the same identity as committer. Do not add Co-authored-by or equivalent attribution for bots, models, agents, or anyone else. Attribute another contributor only when Mete explicitly requests it.

Read the full file on GitHub · 76 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. 3d ago First seen · 76 lines · 1,160 tokens per session scan C 99f862718643

Subscribe to this mod's changes

Remarc AGENTS.md is an instructions file published in the GitHub repository metedata/Remarc (66 stars, last pushed 12d ago), licensed MIT. It adds 1,160 tokens to every session, about $0.0058 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

Peekaboo AGENTS.md

AGENTS.md instructions for openclaw/Peekaboo, covering repository guidelines, start here, project structure & modules, build, test, and development commands and coding style & naming conventions.

openclaw/Peekaboo · 1,070 tokens

Applite CLAUDE.md

Instructions for milanvarady/Applite, covering claude.md, project overview, build & run, architecture and data flow.

milanvarady/Applite · 2,572 tokens

palmier-pro AGENTS.md

AGENTS.md instructions for palmier-io/palmier-pro, covering palmierpro, build, agents, engineering approach and code style.

palmier-io/palmier-pro · 6,680 tokens

scarf AGENTS.md

Instructions for awizemann/scarf: This repo carries its own agent memory — plain files in git, served by the in-repo memophant-mcp MCP server, managed by the Memophant macOS app. It works the same for every agent (Claude Code, Codex, Cursor, Gemini, Copilot). This block is regenerated between the memophant markers…

awizemann/scarf · 1,629 tokens

scarf copilot-instructions.md

Instructions for awizemann/scarf: File memory notes under one of six folders (architecture/conventions/decisions/operations/project/roadmap), never the root. When a note is grounded in code, pass sourcepaths (the repo files it depends on) so Memory Health can drift-check it — an unanchored code note can't be kept…

awizemann/scarf · 461 tokens

mcp-server-apple-events CLAUDE.md

Claude Code instructions for FradSer/mcp-server-apple-events, covering claude.md, commands, run all tests, run a single test file and run tests matching a pattern.

FradSer/mcp-server-apple-events · 2,137 tokens