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/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/mcp/elbwalker/walkeros/flows-flow)<a href="https://agentmods.dev/mcp/elbwalker/walkeros/flows-flow"><img src="https://agentmods.dev/badge/mcp/elbwalker/walkeros/flows-flow/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/mcp/elbwalker/walkeros/flows-flow"><img src="https://agentmods.dev/badge/mcp/elbwalker/walkeros/flows-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
flow 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 1mo 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
{
"flow": {
"command": "npx",
"args": [
"-y",
"@walkeros/mcp"
],
"env": {
"WALKEROS_TOKEN": "",
"WALKEROS_PROJECT_ID": "",
"WALKEROS_APP_URL": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 14 lines scan A f407eb6af908
flow is an MCP server published in the GitHub repository elbwalker/walkerOS (347 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-09-15.
Other mcp servers, from other repositories
shadcnui-jpisnice-react-native
A Model Context Protocol (MCP) server for shadcn/ui components, providing AI assistants with access to component source code, demos, blocks, and metadata. Runs locally from the @jpisnice/shadcn-ui-mcp-server npm package. Needs 1 environment variable to run.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
slack
MCP server "slack" as configured in instructure/instructure-ui. Launched with sh -c set -a; [ -f ./.env ] && . ./.env; set +a; exec npx -y @modelcontextprotoc.
storybook-mcp
MCP server "storybook-mcp", hosted remotely at localhost, as configured in yannbf/mealdrop.
vitex
Generate tailored, ATS-optimized resume PDFs and cover letters from a job description, over MCP. Runs locally from the vitex-cli npm package. Needs 1 environment variable to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.