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/solo-agent/solo/solo-artifactsnpx skills add solo-agent/solo --skill solo-artifactsgit clone --depth 1 https://github.com/solo-agent/soloWrote 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/solo-agent/solo/solo-artifacts)<a href="https://agentmods.dev/skills/solo-agent/solo/solo-artifacts"><img src="https://agentmods.dev/badge/skills/solo-agent/solo/solo-artifacts.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.1 | $0.00040 | $0.00880 |
| Opus 5 | $0.00020 | $0.00440 |
| Sonnet 5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
solo-artifacts 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 6d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
solo-artifacts
Warm Archive fork of work-canvas: produce or publish one self-contained HTML file that renders a Solo task/thread for a human to understand and act on. Prefer the real deliverable over a summary page.
Workflow
-
Publish Existing Deliverable if the current task/run names one.
Trust only explicit current-task evidence, such as:
Deliverable: ./path/to/result.htmlYou may also use a file path named in the current task/thread, or a file you personally created for this task now. Do not scan the workspace by newest file, mtime, or vague filename match; old workspace files can be stale. If several files are named, prefer the product/final deliverable over review/report/panel files unless the user explicitly asks for the review page. Do not switch to review-decision just because the task is in_review.
-
Existing
.html: publish it directly.solo artifact publish --task <task-id> --mode <latest|final> --file <path-to-html> -
Existing
.md,.txt,.json,.csv, or other text/data: create a small self-contained HTML viewer that renders the exact source content, labels the source file near the top, then publish that wrapper. Do not summarize or rewrite the content. -
Multiple deliverables or a directory: create a small index artifact with explicit links/file names and a short note about what each file is.
If a real deliverable exists, stop here.
-
-
Pick the artifact type and read its reference:
The task needs to... Type Read Show where long/messy work stands, what broke, what's next Progress / status report references/progress-report.mdReview analysis or implementation and decide accept/reject/next step Review / decision memo references/review-decision.mdWeigh options head-to-head and pick a winner Comparison / leaderboard references/comparison.mdIf blended, lead with the primary type and borrow blocks from the other.
What ships with it
6 files 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.
- 6d ago First seen · 74 lines · 40 tokens per session scan A 34219ebb36f6
solo-artifacts is a skill published in the GitHub repository solo-agent/solo (546 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 880 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-30.
Other skills, from other repositories
opencode-ensemble
Use when coordinating multiple coding agents, delegating independent software work, managing OpenCode Ensemble teams, choosing teammate roles or models, reviewing teammate output, or deciding whether parallel execution is appropriate.
subagent-model-routing
Route work to non-Claude models (codex/GPT-5.x, Kimi, xAI Grok 4.5, GLM, MiniMax, and local models through opencode custom providers) over the codex/kimi/opencode/grok standalone shims. Supports both one-shot flat dispatch and dependency-ordered DAG orchestration via the Workflow tool. Use when delegating authoring…
magi
Use when the user asks for magi, Open-Magi, @Open-Magi, deliberation, three sages, or multi-agent research.
wiki-ingest
Ingest a source into the project wiki as OKF v0.2 markdown. Point at a file, PR, or doc and the wiki-curator extracts knowledge, writes YAML frontmatter, and updates relevant concept pages.
wiki-lint
Health-check the project wiki for OKF v0.2 conformance — missing frontmatter, missing type:, malformed index.md/log.md, stale pages past staleafter, broken cross-references, and coverage gaps.
learning-systems
Implicit feedback scoring, confidence decay, and anti-pattern detection. Use when understanding how the swarm plugin learns from outcomes, implementing learning loops, or debugging why patterns are being promoted or deprecated. Unique to opencode-swarm-plugin.