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 WizTheAgent/IronMesh --skill ironmesh-statusgit clone --depth 1 https://github.com/WizTheAgent/IronMeshWrote 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/wiztheagent/ironmesh/ironmesh-status)<a href="https://agentmods.dev/skills/wiztheagent/ironmesh/ironmesh-status"><img src="https://agentmods.dev/badge/skills/wiztheagent/ironmesh/ironmesh-status/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/wiztheagent/ironmesh/ironmesh-status"><img src="https://agentmods.dev/badge/skills/wiztheagent/ironmesh/ironmesh-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 24 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00053 | $0.00886 |
| Opus 5.5 | $0.00021 | $0.00354 |
| Sonnet 5.5 | $0.00011 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
ironmesh-status scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "http://127.0.0.1:${IRONMESH_GUI_PORT}/api/mesh_stats?token=${IRONMESH_GUI_TOKEN}" \ How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IronMesh status
Query the local daemon's /api/mesh_stats endpoint and summarize the
mesh's health in one screen.
When to use this
- User asks for mesh health ("status", "is ironmesh up", "peers online")
- Before attempting
ironmesh-sendto a specific peer — verify they're online - As a sanity check after restarting the daemon
How to run
: "${IRONMESH_GUI_PORT:=8766}"
: "${IRONMESH_GUI_TOKEN:?set IRONMESH_GUI_TOKEN from the startup log}"
curl -sS "http://127.0.0.1:${IRONMESH_GUI_PORT}/api/mesh_stats?token=${IRONMESH_GUI_TOKEN}" \
| python3 -c '
import json, sys, datetime
d = json.load(sys.stdin)
print(f"Node: {d[\"name\"]} ({d[\"node_id\"][:12]}...)")
print(f"Uptime: {int(d[\"uptime_seconds\"])}s")
print(f"Peers: {d[\"active_peers\"]}/{d[\"total_peers\"]} online")
lt = d["message_lifetime"]
if lt["count"] > 0:
print(f"Lifetime (n={lt[\"count\"]}): p50={lt[\"p50\"]*1000:.1f}ms p90={lt[\"p90\"]*1000:.1f}ms p99={lt[\"p99\"]*1000:.1f}ms")
else:
print("Lifetime: no samples yet")
print()
print(f"{\"peer\":<16} {\"status\":<9} {\"rtt\":>8} {\"retries\":>8} {\"bytes s/r\":<20}")
for p in d["peers"]:
nid = (p["name"] or p["node_id"])[:16]
online = "online" if p["online"] else "offline"
rtt = f"{p[\"rtt_ms\"]:.1f}ms" if p["rtt_ms"] is not None else "-"
retries = p["retries_total"]
bs = p["bytes_sent_total"]
br = p["bytes_received_total"]
print(f"{nid:<16} {online:<9} {rtt:>8} {retries:>8} {bs:>9}/{br:<9}")
'
Interpreting
- 0 online peers → either you're the only node, or dial is failing. Check the
daemon log for
mDNS tie-breaker/TLS connection failedlines. - retries_total grows on a peer → intermittent link. Check
ironmesh-auditforPEER_DROPPED_LONGevents. - Lifetime p99 > 1s → mesh is congested or a peer is slow to respond. Check per-peer RTT to pinpoint.
- No lifetime samples → no application traffic yet; PING/PONG doesn't count. Send a real MSG through the mesh to populate.
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 First seen · 73 lines · 53 tokens per session scan A 38ea4d861a2f
ironmesh-status is a skill published in the GitHub repository WizTheAgent/IronMesh (25 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 886 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
design-taste-frontend
Use for visual design direction on greenfield, user-facing surfaces — marketing and landing pages, generated apps, portfolio-style or standalone pages. NOT for routine Archestra platform UI work (dashboards, data tables, settings, forms, existing components) — use archestra-dev-frontend for that. Upstream intent…
archestra-docs-writer
Use when writing, editing, restructuring, or auditing Archestra documentation under docs/pages/ — new feature docs, page rewrites, sidebar and information-architecture changes, tone or copy fixes, diagrams, and docs screenshots.
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
archestra-dev-testing
Use for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
migrate-to-archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.
managing-archestra-releases
Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.