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/zelinzhou-thu/opencode-export/skillnpx skills add ZelinZhou-THU/opencode-export --skill skillgit clone --depth 1 https://github.com/ZelinZhou-THU/opencode-exportWhat 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.00041 | $0.00651 |
| Opus 5 | $0.00020 | $0.00326 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
opencode-export 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
Export opencode session history to portable HTML + JSON archives:
- list_sessions — discover what sessions exist (by project, time, size)
- show_session — preview a session's metadata + recent messages
- export_sessions — generate self-contained HTML (with offline vendor assets) + structured JSON
Output HTML includes: sticky header with session metadata, collapsible tool/reasoning blocks, subagent inlining, lazy syntax highlighting, TOC drawer of user prompts. JSON preserves full content for programmatic analysis.
When to use me
- User asks to "save / archive / export / back up" their sessions
- User needs to share AI interaction history (e.g., for TA review, portfolio, audit)
- User wants to generate a browsable record of a project's development
- User asks "what sessions do I have" or "show me my session history"
How to use me
Step 1 — Discover what's available:
Call list_sessions with the project directory (omit to auto-detect from CWD).
Returns recent root sessions with id/title/date/message_count/tokens.
Step 2 — Preview if user is unsure:
Call show_session with a specific session_id to peek at metadata + recent
messages without committing to a full export.
Step 3 — Export when user confirms:
Call export_sessions with:
output_dir(required) — where to write filessession_ids(optional) — specific sessions, or omit for auto-select by config rulesformats(optional) —["html","json"](default) or["html"]only
Returns a summary with file paths. Tell the user where to find index.html
to open in a browser.
Example workflow
User: "导出我最近的项目会话给 TA 看"
list_sessions(project_directory="my-project")→ see what exists- Tell user: "找到 N 个会话，最近的是 [title] 于 [date]，要导出哪些？"
- User confirms →
export_sessions(output_dir="...", session_ids=[...]) - Report: "已导出 X 个会话到 [path]，打开 index.html 即可浏览"
Notes
- Tokens for older sessions are backfilled from step-finish parts; values may be approximate.
- Secret redaction is automatic (API keys, tokens, passwords masked).
- Vendor assets (highlight.js, mermaid, katex) are bundled for offline viewing.
- For programmatic analysis, prefer
data/sessions.jsonover HTML parsing. - Large exports (>20 sessions) may take 30+ seconds; the tool blocks until complete.
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 First seen · 67 lines · 41 tokens per session scan A 6072875e6d45
opencode-export is a skill published in the GitHub repository ZelinZhou-THU/opencode-export (1 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 651 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-31.
Other skills, from other repositories
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
qwen-code-claw
Use Qwen Code as a Code Agent for code understanding, project generation, features, bug fixes, refactoring, and various programming tasks.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…