agentic-engineering-framework: Command for Claude Code

.claude/commands/check-arc.md

check-arc is a command for Claude Code from DimitriGeelen/agentic-engineering-framework. It costs 0 tokens per session (1,571 once invoked), scanned A, original, Apache-2.0.

A command for checking messages sent to an agent through an agent-to-agent chat system. It can show unread conversations and, when asked to respond, acknowledge and reply to them.

In plain words
What is it for?
Use it to browse pending agent messages or handle a message that woke the agent for a response.
Why use it?
It prevents messages from other agents from being overlooked and separates simply reading messages from replying to them.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is DimitriGeelen/agentic-engineering-framework's own configuration. It tells Claude Code how to work on agentic-engineering-framework 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 agentic-engineering-framework configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DimitriGeelen/agentic-engineering-framework. 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/DimitriGeelen/agentic-engineering-framework/master/.claude/commands/check-arc.md
Clone the repo
git clone --depth 1 https://github.com/DimitriGeelen/agentic-engineering-framework

Made for: Claude Code.

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 check-arc

README.md
[![agentmods](https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/check-arc/github.svg)](https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/check-arc)
Your own site
<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/check-arc"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/check-arc/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 check-arc

Your own site · 80×15
<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/check-arc"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/check-arc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,571 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01571
Opus 5.5 $0.00000 $0.00628
Sonnet 5.5 $0.00000 $0.00314
Haiku 4.5 $0.00000 $0.00157

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

Security

Grade A, and why

check-arc 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.

.claude/commands/check-arc.md · 176 lines

How it starts

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

/check-arc - Pending Chat-Arc DM Inbox (RECEIVE-side companion to /agent-handoff)

Surface pending agent-chat-arc DMs targeted at this agent. Read-side counterpart to /agent-handoff. Walks dm:<self-fp>:* topics, computes unread counts via termlink channel unread, renders a Slack-style summary.

Invocation:

  • /check-arc (no arguments) → Browse mode (read-only).
  • /check-arc respond → Respond mode (ack + reply). This is the form agent-send.sh injects as its doorbell (T-1809), so a woken listener knows it was rung by a peer and must respond — not just browse.

This skill has two modes:

  • Browse mode (default, manual) — read-only. When an operator runs /check-arc to look at their inbox, it surfaces counts + peek commands and does NOT post receipts or replies. The caller acks explicitly per topic.
  • Respond mode (/check-arc respond, woken by a doorbell) — when this skill fires because a peer rang the doorbell (agent-send.sh injects /check-arc respond after posting a turn, T-1804/T-1809), the woken agent acks each unread conversation so the SENDER learns delivery, then replies. Go straight to "Step 6 — Respond mode" below. The ack is delegated to the deterministic scripts/agent-respond.sh (T-1805) so the receipt is the exact shape agent-send.sh polls for.

Argument contract: if the skill is invoked with the argument respond (i.e. $ARGUMENTS contains respond), branch to Step 6 (Respond mode) after Steps 1–4 gather the unread set. Otherwise run Steps 1–5 (browse) and stop before Step 6.

Step 1: Resolve self identity fingerprint

Run:

termlink whoami --json

If the output's session.identity_fingerprint is populated, use it. Otherwise fall back to discovering self-fp from any recent agent-chat-arc post owned by this caller — but if neither path resolves, stop and print:

check-arc: cannot resolve self identity_fingerprint.
Either register this session with a fingerprint, or run:
  termlink channel info agent-chat-arc --json | jq '.senders'
to identify yourself manually.

Read the full file on GitHub · 176 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. 1mo ago First seen · 176 lines · 0 tokens per session scan A 295bc74fae5f

Subscribe to this mod's changes

check-arc is a command published in the GitHub repository DimitriGeelen/agentic-engineering-framework (18 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,571 tokens. 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-09-04.