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-trustgit 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-trust)<a href="https://agentmods.dev/skills/wiztheagent/ironmesh/ironmesh-trust"><img src="https://agentmods.dev/badge/skills/wiztheagent/ironmesh/ironmesh-trust/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-trust"><img src="https://agentmods.dev/badge/skills/wiztheagent/ironmesh/ironmesh-trust.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.00488 |
| Opus 5 | $0.00020 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
ironmesh-trust 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 11d 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.
What it actually says
IronMesh trust store operations
The trust store is the TOFU pin database — first-time peer keys are recorded, and subsequent connections claiming the same agent name must present the same Ed25519 identity key.
Subcommands
list
Show every pinned peer and any revocations. Use to answer "who do we trust?" before sending sensitive messages.
ironmesh trust list
revoke <peer-name> — destructive
Adds the peer to the revoked set. The daemon will reject future connections from this peer's identity key even if they present a valid ECDH exchange. Use when:
- A peer has been compromised (stolen laptop, leaked keys)
- A peer is behaving anomalously (replays, bad signatures)
- A node has been decommissioned and you want to block its return
# Requires confirmation — the skill prompts the user first
ironmesh trust revoke compromised-peer
pin <peer-name> <pubkey-b64>
Manually add a peer pin (for offline-first-contact scenarios like bootstrapping a new node from air-gapped keys).
ironmesh trust pin new-peer "mG...base64..."
When to use
- User asks "is X trusted?" →
list - After a
TOFU_MISMATCHevent in the audit log → investigate, then either revoke the old pin (if legitimately rotated) or revoke the incoming peer (if attacker) - New node deploy →
pinfrom the offline key backup
Recovery playbook
See docs/REPIN.md for the full flow: compromised peer → revoke everywhere → verify offline → re-pin or accept TOFU on next contact.
Safeguards in this skill
revokewithout explicit user confirmation → refuseslistis always safe and can be invoked freely- Never auto-pin without user approval — pinning a malicious key would defeat the whole TOFU model
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.
- 11d ago First seen · 68 lines · 41 tokens per session scan A 1012e021c333
ironmesh-trust is a skill published in the GitHub repository WizTheAgent/IronMesh (22 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 488 once invoked, about $0.0002 per session on Opus 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
draw-image
Generate an image from a text prompt using an OpenAI-compatible image generation API (gpt-image-1-mini or compatible). The image is uploaded to the gofile.io public file sharing service and ONLY the public download page URL is returned. Trigger when user asks to draw, paint, generate, or create an image.
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…
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.
archestra-dev-rust-napi
Use when editing Rust in this repo — the NAPI crates under platform/archestra-rs (app-runtime, image, and sandbox core/-rs crate pairs plus napi-loader, with their generated TypeScript bindings) or the standalone ai-labs Rust workspace (core/runner/cli/analyzer/dashboard) — including Rust build/test checks.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
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.