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 Demerzels-lab/elsamultiskillagent --skill stream-of-consciousnessgit clone --depth 1 https://github.com/Demerzels-lab/elsamultiskillagentWrote 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/demerzels-lab/elsamultiskillagent/stream-of-consciousness)<a href="https://agentmods.dev/skills/demerzels-lab/elsamultiskillagent/stream-of-consciousness"><img src="https://agentmods.dev/badge/skills/demerzels-lab/elsamultiskillagent/stream-of-consciousness/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/demerzels-lab/elsamultiskillagent/stream-of-consciousness"><img src="https://agentmods.dev/badge/skills/demerzels-lab/elsamultiskillagent/stream-of-consciousness.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.00034 | $0.03060 |
| Opus 5 | $0.00017 | $0.01530 |
| Sonnet 5 | $0.00007 | $0.00612 |
| Haiku 4.5 | $0.00003 | $0.00306 |
Grade A, and why
stream-of-consciousness 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open-Token Export (SKILL)
Objective
When invoked, output the entirety of the currently available conversation in Open-Token format as a single export artifact, suitable for:
- agent handoff / continuation across runtimes and providers
- audit & incident review
- reproducibility and debugging
- provenance and diffing
The output MUST be machine-parseable and complete per the chosen mode.
Invocation
Parse $ARGUMENTS as space-separated key=value pairs.
Supported options:
-
mode=json|ndjson
Default:json -
pretty=true|false
Default:trueforjson;falseforndjson -
include=visible-only|include-internal
Default:visible-only -
internal=redacted|summary|full
Default:redacted
Meaning:redacted: include internal events only as placeholders (no content)summary: include brief summaries of internal traces (if available)full: include internal traces verbatim (ONLY if available and permitted)
-
redact=none|secrets|pii|strict
Default:secrets -
max_bytes=<int>(optional)
If present, apply truncation rules defined below.
Availability rule for internal traces
If include=include-internal is requested but internal traces (hidden reasoning, hidden system routing, hidden intermediate tokens) are not available in the current runtime context, DO NOT fabricate them.
In that case:
- set
conversation.internal_availability="unavailable" - omit internal-trace content events or export them as redacted placeholders, consistent with
internal=redacted - still export tool calls/results if they are available
Non-negotiable rules
- Export only what is available in the current conversation context; NEVER invent missing turns.
- Preserve causal order; DO NOT reorder events.
- Preserve attribution: correct actor, role, and event type.
- Tool outputs MUST be isolated in
tool_resultevents. - Apply redaction according to the
redactoption (unlessredact=none). - If output is truncated, annotate truncation deterministically (see Truncation section).
- Ensure the final output is valid JSON (or valid NDJSON per line) with no surrounding commentary.
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 · 356 lines · 34 tokens per session scan A 9461c54dbb0c
stream-of-consciousness is a skill published in the GitHub repository Demerzels-lab/elsamultiskillagent (10 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 3,060 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…