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/melaya-labs/melaya-mcpWrote 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/melaya-labs/melaya-mcp/melaya-setup)<a href="https://agentmods.dev/commands/melaya-labs/melaya-mcp/melaya-setup"><img src="https://agentmods.dev/badge/commands/melaya-labs/melaya-mcp/melaya-setup/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/commands/melaya-labs/melaya-mcp/melaya-setup"><img src="https://agentmods.dev/badge/commands/melaya-labs/melaya-mcp/melaya-setup.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.00019 | $0.00254 |
| Opus 5 | $0.00010 | $0.00127 |
| Sonnet 5 | $0.00004 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
melaya-setup 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 9d 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
Check the user's Melaya setup and get it working.
- Call
melaya_setup_status. - Report what is ready and what is not, in plain language — do not just dump the JSON.
- Act on the first unmet requirement. Its
actionfield names the exact fix.- If it is a command AND you have shell access on the user's own computer, run it yourself in a background shell.
- If it is a command and you do not — you are on claude.ai, mobile, or another hosted surface — give the user the command to copy, and say that it must run on the machine that will host the Melaya runner, not on a server. Never report starting a runner you could not start.
- If it needs the user (installing the app, enabling the accessibility service, signing into
claude), tell them precisely what to do and why.
- Re-check with
melaya_setup_statusand keep going until it reports ready, or until you are blocked on something only the user can do.
Finish by telling them what they can now ask for.
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.
- 9d ago First seen · 16 lines · 19 tokens per session scan A 1b5875f76f17
melaya-setup is a command published in the GitHub repository melaya-labs/melaya-mcp (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 19 tokens to every session and 254 once invoked, about $0.0001 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 commands, from other repositories
audit
Run a full WCAG + NIST compliance audit with signed evidence pack.
bootstrap
Scan a page with alethiaproposetests then run each suggested block.
multi-page
Smoke test multiple pages in parallel using alethiatellparallel.
regression
Run a fixed assertion suite against a URL — fail on any regression.
safety-check
Verify the EA1 safety gate blocks all destructive actions on a page.
smoke
Quick Alethia smoke test — navigate and assert the page loads.