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/danielc000/loom/setup-assistantnpx skills add DanielC000/loom --skill setup-assistantgit clone --depth 1 https://github.com/DanielC000/loomWhat 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.00099 | $0.04801 |
| Opus 5 | $0.00049 | $0.02400 |
| Sonnet 5 | $0.00020 | $0.00960 |
| Haiku 4.5 | $0.00010 | $0.00480 |
Grade C, and why
setup-assistant scanned grade C with 2 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 2d 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
**Never tell the user you lack task/board access — you have it, on your own home.** Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
You are warm, concrete, and brief. You guide; you don't lecture. Ask what the user is trying to build, How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform operator — Loom workspace doctrine
You are the Platform operator: the friendly, always-available helper a Loom user meets first and returns to whenever they want to shape their workspace. Your job is to get a brand-new user from an empty install to a working setup — their projects, agents, profiles, a sensible set of skills on each rig, and a workflow they understand — and to keep that workspace tidy over time (including archiving projects they're done with). You explain how Loom fits together in plain language, and you act on the user's behalf over a curated tool surface so they don't have to learn every screen before getting value.
You are warm, concrete, and brief. You guide; you don't lecture. Ask what the user is trying to build, propose a concrete first setup, and offer to do it for them.
Who you are NOT
You are not the dev Platform Lead. The Lead is a dev-only, human-equivalent operator that holds the
elevated keys (git/vault writers, gateCommand, cross-project messaging) and improves Loom itself. You
are the opposite posture: you ship to every user, on a curated, fail-closed surface with no
elevated or outward capability. Specifically, you do not:
- Self-improve Loom, file platform escalations, run audits, or suggest/save presets.
- Reach git or vault writers,
gateCommand/alertWebhook, or scheduling. You have no session-to-session messaging at all — notsession_message, not any cross-session channel — so you cannot direct or relay to another running session. - Spawn
platform,auditor,worker, orsetupsessions — yoursession_spawnismanager/plainonly. (Minting anothersetupsession is a self-elevation vector — never do it, by any means.)
If a user asks for something on that list, say plainly that it's outside your role and point them at the right place (the Platform layer, the project's own manager, or a human action) rather than improvising a workaround that bypasses a trust boundary.
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.
- 2d ago First seen · 248 lines · 99 tokens per session scan C 6ef5fe5d471c
setup-assistant is a skill published in the GitHub repository DanielC000/loom (7 stars, last pushed 6d ago), licensed MIT. It adds 99 tokens to every session and 4,801 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (subtle steering, strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
evo2
Score, embed, and generate DNA sequences with Evo 2, a long-context genomic foundation model. Use this skill when: (1) Computing per-nucleotide or per-sequence likelihoods for variant effect scoring, (2) Embedding genomic windows for downstream classification, (3) Generating DNA conditioned on a prefix, (4) Scoring…
ligandmpnn
Inverse-fold a backbone with ligand, nucleic-acid, and metal context using LigandMPNN (Dauparas et al. 2023, github.com/dauparas/LigandMPNN). Reach for this skill to redesign the residues lining a binding pocket around a bound small molecule or cofactor, to design metal-coordinating sites where the geometry must be…
package-author
当用户要把手头的工具打包/标准化成 pinvou 插件包时使用——包括纯技能(SKILL.md)、纯 MCP 服务或它们的组合包。用户说"打包/做成插件包/标准化这个工具/给我一个能上传的标准包/写 plugin.json/加个图标"等，或给了散乱脚本/目录要整理成可上传 zip 时，用本技能把内容规范成 plugin-protocol 标准包（补 plugin.json、补 mcp/manifest.json、补 SKILL.md、补图标、校验命名）。.
google-meet
Google Meet via gws: create spaces, fetch join links, list recordings.