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 CodeInfinity1/Stram --skill platform-collector-developmentgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/platform-collector-development)<a href="https://agentmods.dev/skills/codeinfinity1/stram/platform-collector-development"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/platform-collector-development/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/codeinfinity1/stram/platform-collector-development"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/platform-collector-development.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.01551 |
| Opus 5 | $0.00026 | $0.00776 |
| Sonnet 5 | $0.00010 | $0.00310 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
platform-collector-development 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 9d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Collector Development
Purpose
Implement Stram platform collectors as organized platform helpers that observe OS or app signals, redact locally, emit shared collector event envelopes, and let the Python runtime own durable ingestion.
When To Use
Use when adding, extending, organizing, reviewing, or debugging collectors under collectors/macos, collectors/windows, or collectors/linux; when wiring a matching Python bridge adapter; or when choosing the right OS API for collector stimuli.
Inputs And Evidence
- User's target OS, collector name, stimulus types, and privacy level.
docs/COLLECTOR_ARCHITECTURE.md.collectors/shared/event-envelope.schema.json.- Existing platform helper layout under
collectors/<os>/. - Relevant Python bridge adapters under
stram/collectors/adapters/and registry wiring instram/collectors/registry.py. - Official OS API docs or man pages for the platform surface. Start with
references/os-api-references.md, then refresh with web lookup when APIs may have changed.
Tool Map
codebase-inspectionskill-authoringread_filesearch_workspacelist_filesrun_shell_commandweb_searchfetch_web_page
Repository Boundaries
- Native code lives only under
collectors/macos,collectors/windows, orcollectors/linux. - Do not add old root-level collector adapters under
stram/collectors. - If Python integration is needed, update only the relevant adapter under
stram/collectors/adapters/and keep registration instram/collectors/registry.py. - Treat JSONL/platform bridge as ingress only. Python owns SQLite event log, consumers, batching, memory, attention compaction, and the LLM boundary.
- Use the existing shared contract at
collectors/shared/event-envelope.schema.json.
Organization Pattern
For each platform, keep helpers modular before adding more collectors:
collectors/<os>/
README.md
shared/event writer or package metadata
host/runtime entrypoint
bridge/spool/health code
collector-category folders
OS support readers
What ships with it
1 file 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.
- 9d ago First seen · 160 lines · 51 tokens per session scan A 33bac1839a91
platform-collector-development is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,551 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-09-03.
Other skills, from other repositories
omh-physical-device-readiness
This is a Hermes-native physical-device-readiness workflow skill.
configure-macro-keyboard
Configure a cheap 3-key USB-C/Bluetooth macro pad on macOS end-to-end with Karabiner-Elements.
wasm
WebAssembly (WASM) integration, WASI, component model, Rust/Go to WASM compilation. Use when implementing WASM modules, browser/edge compute, or polyglot runtime.
emit-fn-key-on-macos
Emit a real Fn key on macOS (for Typeless push-to-talk, macOS dictation, screenshot shortcuts, emoji picker, Spotlight via.
embedded-iot
Embedded systems firmware, microcontrollers (ESP32, STM32, Arduino, Raspberry Pi), RTOS (FreeRTOS, Zephyr), IoT protocols (MQTT, CoAP, BLE), bare-metal C/C++, and hardware peripheral interfaces (I2C, SPI, UART, GPIO). Use when developing firmware, working with microcontrollers, or building IoT devices.
mobile-hardware-ble-nfc
BLE scanning/connecting/GATT operations with react-native-ble-plx, NFC tag reading/writing with react-native-nfc-manager, permissions, background mode, battery-efficient patterns.