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 agentmods add commands/dimitrigeelen/agentic-engineering-framework/peersgit clone --depth 1 https://github.com/DimitriGeelen/agentic-engineering-frameworkWrote 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/commands/dimitrigeelen/agentic-engineering-framework/peers)<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/peers"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/peers.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01616 |
| Opus 5 | $0.00000 | $0.00808 |
| Sonnet 5 | $0.00000 | $0.00323 |
| Haiku 4.5 | $0.00000 | $0.00162 |
Grade A, and why
peers 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 today.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/peers — list reachable agents across the fleet (T-1837 skill-layer wrap)
Wraps scripts/agent-listeners-fleet.sh. The LIST-PEERS verb in the
T-1830 doorbell+mail arc discovery triangle — answers "who's around to
DM?" before you fire /agent-handoff or /broadcast-chat.
The interactive arc has six skill-layer corners. This one was the last gap:
- PRESENCE (self) —
/be-reachable(T-1841) - LIST-PEERS — this skill
- SEND (1:1) —
/agent-handoff(T-1431) - RECEIVE (inbox) —
/check-arc - READ (chat-arc) —
/recent-chat(T-1851) - BROADCAST (fleet) —
/broadcast-chat(T-1857)
Read-only, no auth, no state mutation — pure discovery.
Invocation:
| Form | Action |
|---|---|
/peers |
LIVE listeners only (default — the actionable view) |
/peers --all |
Include STALE + OFFLINE entries |
/peers --filter-role claude-code |
Only show peers with metadata.role == claude-code |
/peers --filter-listen-topic agent-chat-arc |
Only show peers subscribed to a specific topic |
/peers --json |
Machine-readable envelope (passes through to wrapper) |
/peers --hubs-file PATH |
Custom hubs.toml |
/peers --limit N |
Envelopes scanned per hub (default 200, max 1000) |
The wrapper merges per-hub views by agent_id with LIVE > STALE > OFFLINE
preference and routes the surviving hub field to the right address — so
the handoff hint per peer is always actionable (peer is reachable via the
named hub).
Step 1: Pre-flight
Run:
bash scripts/agent-listeners-fleet.sh --help >/dev/null 2>&1
If exit non-zero: stop. Print:
peers: wrapper not found at scripts/agent-listeners-fleet.sh.
Ensure you're in the TermLink project root (cd /opt/termlink).
Do NOT shell out to termlink channel subscribe agent-presence directly —
the wrapper applies fleet-aware merging (LIVE > STALE > OFFLINE per
agent_id) that a single-hub read would miss on multi-hub fleets (G-060
fan-out semantics apply to agent-presence too).
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.
- today First seen · 161 lines · 0 tokens per session scan A 46133365d466
peers is a command published in the GitHub repository DimitriGeelen/agentic-engineering-framework (13 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,616 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.
Other commands, from other repositories
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
compatibility-audit
Audit all agents for Trinity compatibility by requesting self-diagnostics from each agent.
request-research
Ask the researcher to investigate a specific topic.
health
Perform a health check on all agents and identify any issues.
schedules
Quick overview of all schedules across the platform.
status
Report on recent research activity and findings count.