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/kunchenguid/firstmate/process-event-sourcesnpx skills add kunchenguid/firstmate --skill process-event-sourcesgit clone --depth 1 https://github.com/kunchenguid/firstmateWrote 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/kunchenguid/firstmate/process-event-sources)<a href="https://agentmods.dev/skills/kunchenguid/firstmate/process-event-sources"><img src="https://agentmods.dev/badge/skills/kunchenguid/firstmate/process-event-sources.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 | $0.00118 | $0.02951 |
| Opus 5 | $0.00059 | $0.01476 |
| Sonnet 5 | $0.00024 | $0.00590 |
| Haiku 4.5 | $0.00012 | $0.00295 |
Grade A, and why
process-event-sources 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 yesterday.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
process-event-sources
Load this before arming a long-polling source, before registering a deterministic condition->action watch, and whenever a check: wake carries procevent <adapter> <source-id> <sequence>.
The runner exists so a blocking external process never holds firstmate's conversational turn. Firstmate registers a source, keeps working, and is woken when that process completes.
Arming a source
Use the adapter, not the generic runner, for a real source. For a Lavish review artifact firstmate owns (a live investigating scout should host its own loop):
bin/fm-procevent-lavish.sh arm <artifact.html>
When a source carries captain answers to captain-held tasks, bind it BEFORE arming it, so it can never produce an answer that has nowhere to go:
bin/fm-captain-hold.sh bind <source-id>
The runner then passes each captured result to that source's own adapter answers command and pipes the keyed answers it prints into the one keyed-answer intake, which owns every rule about what they mean; the keys are captain-held task ids.
This is generic across built-in adapters with an answers command, and the runner still wakes you to act on the result.
External process-event bindings intentionally expose no answer operation and cannot feed the captain-answer intake.
captain-hold-lifecycle owns when a binding is required and what the keys must be.
A configured remote secondmate reply source is armed and handled through bin/fm-procevent-remote-reply.sh.
Its header owns exact commands, while the adapter owns cursor continuity, validated deduplicated status ingest, path-confined document fetch, acknowledgement, and re-arming after a good delta.
A continuity break is escalated once and stays unarmed until an operator deliberately rebases it.
For a recurring mid-task quota check, arm the quota adapter:
bin/fm-procevent-quota.sh arm [--interval <secs>] [--threshold <percent>] [--provider <provider>]
It keeps polling through unknown quota and wakes when known quota drops below the configured threshold, runway becomes exhausted_now, or polling fails.
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.
- yesterday Changed · +9 lines 29fc2df8bf70
- 4d ago First seen · 129 lines · 118 tokens per session scan A c19eb9f31a0d
process-event-sources is a skill published in the GitHub repository kunchenguid/firstmate (4,724 stars, last pushed today), licensed MIT. It adds 118 tokens to every session and 2,951 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…