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.
git clone --depth 1 https://github.com/MosaicXR-AI/mosaic-bridgeWrote 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/agents/mosaicxr-ai/mosaic-bridge/mosaic-shader)<a href="https://agentmods.dev/agents/mosaicxr-ai/mosaic-bridge/mosaic-shader"><img src="https://agentmods.dev/badge/agents/mosaicxr-ai/mosaic-bridge/mosaic-shader/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/agents/mosaicxr-ai/mosaic-bridge/mosaic-shader"><img src="https://agentmods.dev/badge/agents/mosaicxr-ai/mosaic-bridge/mosaic-shader.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00120 | $0.01012 |
| Opus 5 | $0.00060 | $0.00506 |
| Sonnet 5 | $0.00024 | $0.00202 |
| Haiku 4.5 | $0.00012 | $0.00101 |
Grade A, and why
mosaic-shader 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 12d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 12d ago First seen · 92 lines · 120 tokens per session scan A 5f22b31a6152
mosaic-shader is an agent published in the GitHub repository MosaicXR-AI/mosaic-bridge (10 stars, last pushed yesterday), with no licence file. It adds 120 tokens to every session and 1,012 once invoked, about $0.0006 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-31.
Other agents, from other repositories
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
unity-diagnostics
Use to investigate Unity connection, compilation, console, scene-health, runtime-state, rendering, memory, or performance problems through Unity Biome MCP. Do not use to implement fixes.
megalinter-runner
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
megalinter-fixer
Fix the errors reported by ONE MegaLinter linter, following the linter's fix guide. Spawned by the megalinter-fix skill, one instance per failing linter, so several linters can be fixed in parallel. Edits source files but never commits, pushes, or disables anything (linters, rules, inline suppressions) — disables are…
megalinter-watcher
Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.
build-error-resolver
Build and TypeScript error resolution specialist — large diagnostic context, root-cause triage across tsc/lint/webpack/vite. Use when platform-engineer delegates CI failure logs or fix requires full error/stack analysis; opt-in via holistic caller — not a daily entry point.