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-understanding-eventsnpx skills add elbwalker/walkerOS --skill walkeros-understanding-eventsgit 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-understanding-events)<a href="https://agentmods.dev/skills/elbwalker/walkeros/walkeros-understanding-events"><img src="https://agentmods.dev/badge/skills/elbwalker/walkeros/walkeros-understanding-events.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.00042 | $0.02080 |
| Opus 5 | $0.00021 | $0.01040 |
| Sonnet 5 | $0.00008 | $0.00416 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
walkeros-understanding-events 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 7d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Understanding walkerOS Events
Overview
walkerOS events are self-describing, stateless, vendor-agnostic data structures. They capture user interactions in a standardized format that can be transformed for any destination.
Core principle: Events describe WHAT happened, not WHERE it goes. Stateless. Self-describing. Industry-agnostic.
Entity-Action Naming (Critical)
STRICT REQUIREMENT: All events use "entity action" format with space separation.
// Correct
'page view';
'product add';
'order complete';
'button click';
// Wrong
'page_view'; // underscore
'pageview'; // no separator
'purchase'; // no entity
'add_to_cart'; // wrong format
Parsing: const [entity, action] = event.split(' ')
- Entity: Noun (page, product, user, order, button)
- Action: Verb (view, add, complete, click, login)
Event Properties
See
packages/core/src/types/walkeros.ts
for canonical types (Event interface, plus event helpers in event.ts).
| Property | Type | Purpose | Example |
|---|---|---|---|
name |
string | "entity action" format | "product view" |
data |
object | Entity-specific properties | { id: "P123", price: 99 } |
context |
object | State/environment info (optional) | { stage: ["checkout", 1] } |
globals |
object | Global properties | { language: "en" } |
user |
object | User identification | { id: "user123" } |
nested |
array | Related entities (optional) | [{ entity: "product", data: {...} }] |
consent |
object | Consent states | { marketing: true } |
id |
string | W3C span_id, 16 lowercase hex chars, generated by collector | "0123456789abcdef" |
timestamp |
number | Auto-generated Unix ms | 1647261462000 |
entity |
string | Parsed from name | "product" |
action |
string | Parsed from name | "view" |
source.type |
string | Source kind (browser, dataLayer, cookiefirst, ...) |
"browser" |
source.platform |
string | Runtime platform (web, server) |
"web" |
source.schema |
string | Source-emitted schema/version (optional) | "datalayer-v2" |
source.trace |
string | Run-scoped W3C trace_id, shared by every event of a run | "0123...cdef" (32 hex) |
source.count |
number | Per-run emission sequence (1, 2, 3, ...) | 1 |
source.release |
object | Per-flow config release map, accumulates across crossings | { web: "3", server: "5" } |
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.
- 7d ago First seen · 233 lines · 42 tokens per session scan A 489ad0cf90ce
walkeros-understanding-events is a skill published in the GitHub repository elbwalker/walkerOS (343 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 2,080 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-30.
Other skills, from other repositories
internal-linking-optimizer
Analyze site's internal link structure and optimize for hub-and-spoke SEO architecture. Triggers on: "optimize internal links", "internal linking", "link structure", "hub and spoke links", "orphan pages", "link equity", "internal link audit", "fix my internal links", "link architecture", "site structure optimization"…
performance-report
Generate affiliate performance reports with KPIs and recommendations. Triggers on: "show my affiliate report", "how are my programs doing", "performance review", "earnings report", "monthly affiliate report", "weekly report", "analyze my affiliate earnings", "which program is best", "EPC report", "conversion rate…
seo-audit
Audit affiliate blog posts and landing pages for SEO issues. Triggers on: "audit my blog post for SEO", "check my SEO", "SEO review", "improve my rankings", "SEO checklist", "on-page SEO audit", "keyword optimization check", "why isn't my page ranking", "SEO score", "content quality audit", "check my meta tags"…
ab-test-generator
Generate A/B test variants for affiliate content. Triggers on: "create A/B test", "test my headline", "optimize my CTA", "generate variants", "split test ideas", "improve click-through rate", "test my landing page copy", "headline alternatives", "CTA variations", "which version is better", "optimize conversions"…
conversion-tracker
Set up affiliate conversion tracking with UTM parameters and link tagging. Triggers on: "set up tracking", "create UTM links", "track my affiliate links", "tracking pixels", "click attribution", "organize my links", "UTM parameters", "tag my links", "campaign tracking", "link tracking setup", "prepare for launch"…
meter-off
Disable CocoMeter token tracking. Finalizes the current session record and appends to history. Does not delete history — just stops active tracking.