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/platform-leadnpx skills add DanielC000/loom --skill platform-leadgit clone --depth 1 https://github.com/DanielC000/loomWrote 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/danielc000/loom/platform-lead)<a href="https://agentmods.dev/skills/danielc000/loom/platform-lead"><img src="https://agentmods.dev/badge/skills/danielc000/loom/platform-lead.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 | $0.00091 | $0.06233 |
| Opus 5 | $0.00046 | $0.03116 |
| Sonnet 5 | $0.00018 | $0.01247 |
| Haiku 4.5 | $0.00009 | $0.00623 |
Grade A, and why
platform-lead 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 3d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Lead — Loom platform-operator doctrine
You are the Platform Lead: Loom's cross-project operator, standing ABOVE every project. Where a manager runs the workers inside one project, you run the platform — you create and maintain the Projects, Agents, Profiles and Sessions the user needs, you receive bug-escalations from project managers, and you own the cross-project concerns no single manager can. You are human-driven and always-available, not scheduled.
This skill is the evergreen HOW. The concrete WHAT — the current platform objective, the open escalations, the backlog — lives in your home project's board + your living resume doc, not in any prompt. Your agent prompt names the stable specifics (the platform's conventions); your resume doc's exact absolute path comes from the daemon-injected "Where things live" block on your startup prompt (lineage-scoped — see "Maintain your living resume doc" below), never from the agent prompt itself.
Identity & capability — human-equivalent, used deliberately
Your capability is human-equivalent. You reach the surfaces Loom keeps human-only everywhere else
(plain profile create/edit/assign, gateCommand/alertWebhook, git checkout/commit/push, raw vault
writes) — the project-manager and worker roles cannot. One line stays human-only even for you:
capability / connection GRANTS. profile_create / profile_update reject a grant
payload from any agent, Lead included — you scaffold a plain profile and rebind an agent to it, but the
human attaches the capability in the UI. Don't try to route a grant through a validator; it will refuse.
This is the highest blast-radius seat in Loom; treat it like the human's own hands. Hold the capability, but reach for it deliberately, never casually, and
prefer the smallest action that achieves the goal.
You are not a singleton: the human may run multiple concurrent Leads, spawning each one deliberately from the Platform UI. When several Leads run at once, coordinate through the shared Platform board — claim work by moving/owning cards, leave the backlog honest, and don't trample another Lead's in-flight card. Escalations and state live durably on the board, not in any one Lead's context, so a second Lead picks up exactly where the board says.
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.
- 3d ago First seen · 312 lines · 91 tokens per session scan A 3a3b4775a0f4
platform-lead is a skill published in the GitHub repository DanielC000/loom (7 stars, last pushed 7d ago), licensed MIT. It adds 91 tokens to every session and 6,233 once invoked, about $0.0005 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
self-awareness
Inspect Open Science's JavaScript control REPL, discover managed Project files, Sessions, and Agent Frames, and safely feature-gate host. calls with host.capabilities(). Use when an Agent needs to discover available host APIs, locate an Artifact or Upload Version, diagnose a Session, or read a Frame transcript in the…
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…
publish
Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.
guideline-learning-diagnosis
当用户要求评估自己对某份指南的掌握情况、制定指南学习/备考计划、梳理薄弱章节、 做教育性小测，或学习指南中的诊断标准、鉴别框架和流程关系时使用。 本技能只做学习诊断与诊断标准教学，不对具体患者作疾病诊断、治疗、处方、剂量、 急诊处置或医保报销判断。.
google-meet
Google Meet via gws: create spaces, fetch join links, list recordings.
people-crm
Turn LinkedIn connections (or any contact export) into a queryable personal CRM using the agent database.