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/loom-session-endnpx skills add DanielC000/loom --skill loom-session-endgit 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/loom-session-end)<a href="https://agentmods.dev/skills/danielc000/loom/loom-session-end"><img src="https://agentmods.dev/badge/skills/danielc000/loom/loom-session-end.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.00053 | $0.00644 |
| Opus 5 | $0.00026 | $0.00322 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
loom-session-end 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 4d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session End (Loom)
Leave the work picked-up-able by the next session. The board is the source of truth; the vault holds prose. The daemon auto-commits the vault — never run manual vault git.
Steps
- Update the board task (
tasks_update): note what was completed in the body, record decisions + their rationale, and add items for what remains. Move the task to its correct column by ROLE (review / terminal / parked). Only move to a terminal column if it's actually true — scoped work outstanding means it isn't done. - Code state — ensure the build/gate passes; commit only if asked. Report any uncommitted changes
plainly. When you do commit, stage an explicit list of the paths this session touched
(
git add <path> …) — nevergit add -Aorgit add .in a shared workspace: other unrelated in-flight work may be present and a blanket stage would sweep it into your commit. Its subject follows the card's Conventional-Commits title (type(scope): summary). Push with plaingit push(it already refuses a non-fast-forward — there is no valid--ff-onlypush flag); reach for--force-with-leaseonly as a deliberate guard when a force is genuinely intended. - Prose — if you changed design/architecture notes in the project's vault, apply
/loom-doc-hygiene(rewrite in place, no contradictions, bounded). - Living resume doc (leads) — if you keep one, make sure it's current: what's merged, the prioritized backlog, key decisions, where things stand. A successor should be able to read it cold.
- Summary — a short, factual wrap-up: what shipped, what's verified, what's left.
By role
- Worker: finish with
worker_report—done(one-line summary + key decisions) orblocked(withneeds). Don't merge; your manager reviews and gates. See/worker. - Manager near your context window: hand OFF YOURSELF via
recycle_me, seeding the successor from your living resume doc (worker_recycleis for recycling a subordinate worker, not yourself). See/orchestrate.
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.
- 4d ago First seen · 45 lines · 53 tokens per session scan A 5cd4611442c6
loom-session-end is a skill published in the GitHub repository DanielC000/loom (7 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 644 once invoked, about $0.0003 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
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).
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…
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…
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.