Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/nano-step/embrace-readonly-mcp/embrace-readonly-full-data)<a href="https://agentmods.dev/skills/nano-step/embrace-readonly-mcp/embrace-readonly-full-data"><img src="https://agentmods.dev/badge/skills/nano-step/embrace-readonly-mcp/embrace-readonly-full-data/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/nano-step/embrace-readonly-mcp/embrace-readonly-full-data"><img src="https://agentmods.dev/badge/skills/nano-step/embrace-readonly-mcp/embrace-readonly-full-data.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.00036 | $0.01065 |
| Opus 5 | $0.00018 | $0.00532 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
embrace-readonly-full-data 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embrace read-only full data
Use embrace_list_readonly_tools to inspect the published tool schemas, then use
embrace_call_readonly with the exact remote tool name and JSON arguments.
The proxy preserves the complete official response, including structuredContent,
metadata, group IDs, and crash sample session IDs. Prefer a narrow time window,
app version, message filter, and limit when possible; expand only when needed.
Complete official tool map
Use embrace_call_readonly with these remote tool names. For repeatable local smoke tests or when a host has not inherited the environment, use the prebuilt scripts/embrace_mcp_call.py; do not generate a new client script. The CLI accepts a tool name and a JSON object via --arguments and preserves the proxy's full JSON output.
zsh -lic 'uv run --project /Users/tamlh/workspaces/self/AI/Tools/embrace-readonly-mcp python /Users/tamlh/workspaces/self/AI/Tools/embrace-readonly-mcp/scripts/embrace_mcp_call.py embrace_list_readonly_tools'
App and sessions
list_apps: discover app IDs, platforms, regions, and latest versions.get_app_details: sessions, unique users, crash-free rate, and version totals.get_top_versions: version adoption.get_session_distribution: session breakdown by app version, OS, country, device, or manufacturer.
Logs and exceptions
list_logs: find log groups and obtaingroup_idvalues.get_log_details: counts, trends, templates, and token analysis for one log group.get_log_distribution: break a log group down by version, OS, country, device, or environment.list_exceptions: find web/Unity/Flutter exception groups.get_exception_details: inspect one exception group.
Crashes and debug traces
list_crashes: find crash groups and obtaingroup_idvalues.get_crash_details: crash impact, versions, foreground rate, and top frame.get_crash_stack_samples: full representative stack frames, timestamps, devices, andsession_idvalues.get_crash_distribution: crash breakdown by version, OS, country, or device.list_root_spans: find slow or failing root operations.get_root_span_stats: timing and outcome statistics for one root span.get_root_span_distribution: root-span breakdown by version, OS, country, or device.
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 · 98 lines · 36 tokens per session scan A 7f96e914909d
embrace-readonly-full-data is a skill published in the GitHub repository nano-step/embrace-readonly-mcp (0 stars, last pushed 16d ago), licensed MIT. It adds 36 tokens to every session and 1,065 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.