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 skills add elbwalker/walkerOS --skill walkeros-using-cligit 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-using-cli)<a href="https://agentmods.dev/skills/elbwalker/walkeros/walkeros-using-cli"><img src="https://agentmods.dev/badge/skills/elbwalker/walkeros/walkeros-using-cli/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/elbwalker/walkeros/walkeros-using-cli"><img src="https://agentmods.dev/badge/skills/elbwalker/walkeros/walkeros-using-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 374 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 438 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 490 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00047 | $0.09952 |
| Opus 5.5 | $0.00019 | $0.03981 |
| Sonnet 5.5 | $0.00009 | $0.01990 |
| Haiku 4.5 | $0.00005 | $0.00995 |
Grade A, and why
walkeros-using-cli 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 2d 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 — 900 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using the walkerOS CLI
Overview
The walkerOS CLI (walkeros) validates, simulates, tests and bundles event
collection flows. It does not run them: a built server flow runs with
runneros start from @walkeros/runner (the walkeros/flow image).
Core workflow:
- Configure - Write Flow.Json JSON config
- Validate -
walkeros validate flow.json - Test - Simulate events (mocked) or push (real)
- Bundle -
walkeros bundle flow.json -o dist/ - Run -
runneros start dist/flow.mjs, or deploy through the app
Quick Start
# Install
npm install -g @walkeros/cli
# Bundle a flow
walkeros bundle flow.json
# Test with simulated event
walkeros push flow.json -e '{"entity":"page","action":"view"}' --simulate destination.demo
# Push real event
walkeros push flow.json -e '{"entity":"page","action":"view"}'
Commands Overview
| Command | Purpose | Safe? |
|---|---|---|
bundle |
Generate JS bundle from config | ✅ |
push |
Execute with real API calls (or --simulate for mocked) |
⚠️ |
setup |
Run a component's setup() to provision external resources |
⚠️ |
validate |
Validate configs/events | ✅ |
cache |
Manage caching | ✅ |
auth |
Log in, log out, check identity, print the access token | ✅ |
api |
Call the walkerOS app API, or list its operations | ⚠️ |
For detailed command reference, see commands-reference.md.
Common Workflows
Development Workflow
1. Write flow.json config
2. Bundle: walkeros bundle flow.json
3. Simulate: walkeros push flow.json -e event.json --simulate destination.demo
4. Fix issues, repeat 2-3
5. Push test: walkeros push flow.json -e event.json
6. Deploy: in the walkerOS app, or
walkeros api POST /api/projects/{projectId}/flows/<flowId>/deploy
(see the CI recipe in the CLI docs)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · -7 lines d454f41e2f1e
- 3d ago Changed · +2 lines d8ef436f72b2
- 10d ago Changed · +4 lines e98536cbb8e2
- 13d ago Changed · +16 lines 47e932ae0ff9
- 15d ago Changed · +8 lines c20aedb9e886
- 17d ago Changed · +87 lines 0b3be4ff96ca
- 23d ago Changed · +145 lines · +13 tokens per session 50a7a1ec3088
- 24d ago Changed · +2 lines 4af6114bd5cb
- 1mo ago First seen · 643 lines · 34 tokens per session scan A 9ad449828914
walkeros-using-cli is a skill published in the GitHub repository elbwalker/walkerOS (348 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 9,952 once invoked, about $0.0002 per session on Opus 5.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
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
fixing-flaky-tests
Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when hogli ci:insights or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a…
qa-frontend
Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence, or to make a feature reel (see reel mode…
writing-tests
Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a…
creating-online-evaluations
Author continuously-running online evaluations in PostHog AI observability, grounded in real failure modes you've identified. Use when the user wants evaluations that automatically score new generations or whole traces going forward — "create an eval to catch X", "continuously check that responses do Y", "turn these…
auditing-warehouse-source-coverage
Audit already-implemented Data warehouse import sources for endpoints, schemas, and tables the vendor's API offers but we never wired up. Use when asked whether a source is missing endpoints, to find new endpoints a vendor has added since a source was built, to refresh COVERAGEGAPS.md, to prioritize which source to…