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 agentmods add skills/elbwalker/walkeros/walkeros-mcp-actionsnpx skills add elbwalker/walkerOS --skill walkeros-mcp-actionsgit clone --depth 1 https://github.com/elbwalker/walkerOSWrote 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/elbwalker/walkeros/walkeros-mcp-actions)<a href="https://agentmods.dev/skills/elbwalker/walkeros/walkeros-mcp-actions"><img src="https://agentmods.dev/badge/skills/elbwalker/walkeros/walkeros-mcp-actions.svg" alt="Measured on agentmods" 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.00062 | $0.01421 |
| Opus 5 | $0.00031 | $0.00711 |
| Sonnet 5 | $0.00012 | $0.00284 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
walkeros-mcp-actions 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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calling walkerOS MCP Tools from Code
When to Use This Skill
You are an AI agent running inside a code-execution host, not issuing tool calls one at a time through the model. Examples:
- Claude Code in code-execution / "Code Mode"
- a Cloudflare Worker or other serverless sandbox
- an app's server-side sandbox that binds the walkerOS MCP transport
The pattern: bind the MCP transport once, call only the tools you need from
code, filter the verbose structuredContent payload in code, and return
only the distilled answer to the model. This suppresses tokens that the model
never needs to see (full catalogs, per-destination simulation dumps) and avoids
a chain of one-by-one tool calls.
This is the "Code Execution with MCP" / "Code Mode" pattern: treat MCP tools as functions you call in a sandbox, not as round-trips through the model context.
The Seven Pure Tools
These walkerOS MCP tools are pure and composable: same input, same output, no auth, no cloud side effects. Safe to call freely from code.
| Tool (fully-qualified) | Purpose | Verbose output worth filtering |
|---|---|---|
walkeros:flow_validate |
Validate a flow or step config; return issues | small |
walkeros:flow_simulate |
Run a flow against an event, mock destination calls | yes (per-destination calls) |
walkeros:flow_bundle |
Bundle a flow config to a JS artifact | medium (bundle/meta) |
walkeros:flow_examples |
Fetch canonical flow/step examples | yes (many examples) |
walkeros:package_search |
Find packages by type/platform/keyword | yes (catalog) |
walkeros:package_get |
Read a package's schemas, hints, examples | yes (full schemas) |
walkeros:diagnostics |
Report MCP/CLI versions, app URL, reachability | small |
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.
- 6d ago First seen · 128 lines · 62 tokens per session scan A f63cbda702ba
walkeros-mcp-actions is a skill published in the GitHub repository elbwalker/walkerOS (343 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,421 once invoked, about $0.0003 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
task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation.
meter-off
Disable CocoMeter token tracking. Finalizes the current session record and appends to history. Does not delete history — just stops active tracking.
meter-on
Enable CocoMeter token and credit tracking for this session. Creates tracking state in .cocoplus/meter/ and activates per-tool token capture via post-tool-use hook.
solr-semantic-search
To build Solr phrase-tagging semantic search: concept tagging, taxonomy, graph paths.
tao-train-sparse4d
Sparse4D for multi-camera temporal 3D object detection and tracking. Uses sparse queries with deformable attention across camera views and time for end-to-end 3D perception, with an instance bank for temporal tracking. Use when training, evaluating, exporting, quantizing, or running inference for a TAO Sparse4D model.…
logistics-ops
Use when an order is paid and packed and the box now has to move, go sideways, or come back — picking a carrier and service and cutting a label, reacting to a delivery exception, getting ahead of where-is-my-order tickets, running a return, exchange or refund with its reverse label, filing a carrier claim before the…