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 deepelementlab/jupyter-studio --skill opencodegit clone --depth 1 https://github.com/deepelementlab/jupyter-studioWrote 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/deepelementlab/jupyter-studio/opencode)<a href="https://agentmods.dev/skills/deepelementlab/jupyter-studio/opencode"><img src="https://agentmods.dev/badge/skills/deepelementlab/jupyter-studio/opencode/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/deepelementlab/jupyter-studio/opencode"><img src="https://agentmods.dev/badge/skills/deepelementlab/jupyter-studio/opencode.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.00038 | $0.01114 |
| Opus 5.5 | $0.00015 | $0.00446 |
| Sonnet 5.5 | $0.00008 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
opencode 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode CLI (clawcode)
Use OpenCode as an external coding agent when the user wants OpenCode specifically.
Do not confuse these entry points (they are not interchangeable):
| Entry | Role |
|---|---|
/opencode-cli (TUI slash) |
One-shot probe or command via opencode_cli_bridge: merged stdout/stderr, not a PTY session and not multi-turn TUI control. Default args often --version. |
bash |
One-shot shell in agent turns, e.g. opencode run '…'. |
terminal + process (Agent tools) |
Multi-turn driving of a background shell/OpenCode TUI: terminal with background=true (and pty=true on POSIX with clawcode[terminal-pty]), then process for poll / submit / kill. Requires CLAWCODE_TERMINAL_ENV=local for full PTY on Linux/macOS; Windows host is limited—use WSL or Linux for interactive TUI automation. |
Optional: pip install 'clawcode[terminal-pty]' for ptyprocess on POSIX.
When to use
- User asks to use OpenCode or
opencode. - You need a bounded task: prefer
opencode run '...'via bash in the project workspace. - You only need to verify the CLI is installed:
/opencode-cli(defaultopencode --version) after/claw; same terminal stack as/claude-cli(CLAWCODE_TERMINAL_ENV/TERMINAL_ENV).
Prerequisites
- Install OpenCode (e.g.
npm i -g opencode-ai@latestor vendor instructions). - Auth:
opencode auth loginor provider env vars (see OpenCode docs). - Check:
opencode auth listshould list at least one provider when run in the same environment as the agent.
clawcode-specific capabilities
| Goal | What to use |
|---|---|
| Quick probe (version, install check) | /opencode-cli only—single run, not multi-turn. Same Claw gate as /claude-cli. |
| Run a command in agent turns | bash: e.g. opencode run 'your task' with working_directory set to the repo root. |
| Docker/SSH terminal backend | Same as bash: settings.shell.use_environments_backend and CLAWCODE_TERMINAL_*; ensure the image or remote has opencode on PATH. |
| Interactive OpenCode TUI (agent-driven) | terminal (background=true, pty=true where supported) + process (poll / submit / …). Non-local backends: log-polled background only (no stdin). Optional check_interval on terminal schedules completion notifications in the TUI (see CLAW_SUPPORT_MAP.md). |
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.
- 1mo ago First seen · 84 lines · 38 tokens per session scan A 425dbf455f50
opencode is a skill published in the GitHub repository deepelementlab/jupyter-studio (14 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,114 once invoked, about $0.0002 per session on Opus 5.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
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
cognitive-doc-design
Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.