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 skills add metedata/Remarc --skill skillgit clone --depth 1 https://github.com/metedata/RemarcWrote 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/skills/metedata/remarc/skill)<a href="https://agentmods.dev/skills/metedata/remarc/skill"><img src="https://agentmods.dev/badge/skills/metedata/remarc/skill/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/skills/metedata/remarc/skill"><img src="https://agentmods.dev/badge/skills/metedata/remarc/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.02843 |
| Opus 5.5 | $0.00016 | $0.01137 |
| Sonnet 5.5 | $0.00008 | $0.00569 |
| Haiku 4.5 | $0.00004 | $0.00284 |
Grade A, and why
remarc 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remarc Comments
Remarc comments are contextual feedback attached to a session. Infer the user's intent from the whole request, not from one exact verb. People may say "check", "review", "handle", "go through", "fix these", "take this", "what's left", "triage", or many other variants.
Default to an addressing workflow when the user asks you to take responsibility for the comments. Use a read-only workflow when the user asks only to inspect, list, summarize, count, audit, or recommend without changing the underlying artifact or comment statuses.
Session Lifecycle
Remarc sessions are containers for contextual feedback. They may be created by the user from the Remarc app, created by chat through MCP, or created by an installed integration. Do not assume the session's origin.
Use remarc_create_session only when the user asks to start a Remarc session
mid-conversation. Claude Code and Codex must provide their real agent session
ID; do not invent one. OMP may omit the legacy session ID because its trusted
MCP process records origin: "omp", then the user can run /remarc-pair to
enable instant delivery. For existing work in any harness, list sessions first
and reuse the match when appropriate.
There is no exposed MCP tool to stop, close, or delete a session. If the user asks to stop a session, explain that MCP cannot do that directly and point them to the Remarc app's session controls or their configured integration cleanup.
Choose a Mode
Before changing any status, decide which mode the user requested:
- Read-only: Inspect, list, count, summarize, audit, or recommend. Do not change statuses.
- Addressing: Take responsibility for comments, update the artifact or produce the requested response, and move comments through the status lifecycle.
- Status-only: Change Remarc statuses exactly as requested without doing additional artifact work.
If the request is ambiguous and status changes would surprise the user, ask a brief clarifying question. If the user has clearly handed you the comments to work through, use addressing mode.
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 Changed · +24 lines 739c1eee609e
- 1mo ago First seen · 236 lines · 41 tokens per session scan A 2285fd642762
remarc is a skill published in the GitHub repository metedata/Remarc (80 stars, last pushed 13d ago), licensed MIT. It adds 41 tokens to every session and 2,843 once invoked, about $0.0002 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 skills, from other repositories
skeleton
Extract and navigate a compact structural map and implementation-risk signals for a codebase with the skltn CLI, including declarations, signatures, inheritance, source ranges, parser-range-derived implementation fingerprints, and project-context heuristics. Use when exploring architecture, locating symbols, reviewing…
swift-focusengine-pro
Reviews, writes, and fixes focus management code for all Apple platforms (tvOS, iOS/iPadOS, watchOS, visionOS, macOS), covering SwiftUI, UIKit, AppKit, and RealityKit. Use when reading, writing, or reviewing apps that handle focus, hover, key view loops, or Digital Crown navigation.
swift-concurrency-pro
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.
scarf-miniapp-author
Author a Scarf mini-app — a small sandboxed web surface (HTML/CSS/JS) that renders inside a project's cockpit and talks to the bound Hermes session + project data through the versioned window.scarf bridge. Use to build a bespoke panel (a task board, an approval queue, a chart, a data table) for a project.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
review-preflight
Review tooling for a PR: review-preflight prints REVIEW.md's criteria and the PR's live gate state before a review; ci-triage maps a PR's failing checks to already-filed issues.