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/mikeprasad/aria-knowledge/clip-threadnpx skills add mikeprasad/aria-knowledge --skill clip-threadgit clone --depth 1 https://github.com/mikeprasad/aria-knowledgeWrote 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/mikeprasad/aria-knowledge/clip-thread)<a href="https://agentmods.dev/skills/mikeprasad/aria-knowledge/clip-thread"><img src="https://agentmods.dev/badge/skills/mikeprasad/aria-knowledge/clip-thread.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.00140 | $0.02066 |
| Opus 5 | $0.00070 | $0.01033 |
| Sonnet 5 | $0.00028 | $0.00413 |
| Haiku 4.5 | $0.00014 | $0.00207 |
Grade A, and why
clip-thread 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 153 lines · 140 tokens per session scan A 9013813418d9
clip-thread is a skill published in the GitHub repository mikeprasad/aria-knowledge (16 stars, last pushed 7d ago), with no licence file. It adds 140 tokens to every session and 2,066 once invoked, about $0.0007 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
video
Use when a brief has to become a film. Turns a one line ask into a Claude Design prompt written in the animations-v3 engine's own language, plus the built piece.jsx and a contact sheet to look at before anyone renders. Covers reference roles, the kit, the storyboard gate, the motion floor, and the verification…
emulo
Use when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history and native emulo:mine is not available. This is the cross-agent skills.sh bootstrap, not the native namespaced plugin.
emulo
Load the user's Emulo profile, mined from their local Claude Code, Codex, and OpenCode session logs, so you work like them instead of a cold start. Use before working on their task.
mine
Use only when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history.
write
Use for marketing, social, replies, product copy, launch copy, and writing in the user's voice when their Emulo writing profile should guide the task. Do not use for unrelated execution or UI/UX design alone.
design
Use for UI, UX, visual hierarchy, frontend-design judgment, references, redesigns, and design critique when the user's Emulo taste should guide the task. Do not use for unrelated execution or marketing/social writing alone.