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.
git clone --depth 1 https://github.com/dasein108/yt-mem-aiWrote 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/commands/dasein108/yt-mem-ai/yt-digest)<a href="https://agentmods.dev/commands/dasein108/yt-mem-ai/yt-digest"><img src="https://agentmods.dev/badge/commands/dasein108/yt-mem-ai/yt-digest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dasein108/yt-mem-ai/yt-digest"><img src="https://agentmods.dev/badge/commands/dasein108/yt-mem-ai/yt-digest.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00080 |
| Opus 5 | $0.00005 | $0.00040 |
| Sonnet 5 | $0.00002 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
yt-digest 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 12d 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.
What it actually says
Use the yt-agent skill, scenario B (daily digest)$ARGUMENTS
Run discover + fetch-pending, analyze each of the day's transcribed videos,
and compose digests/<DATE>.md (executive digest + one section per video).
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.
- 12d ago First seen · 10 lines · 10 tokens per session scan A 7b647ff566d0
yt-digest is a command published in the GitHub repository dasein108/yt-mem-ai (7 stars, last pushed 20d ago), licensed MIT. It adds 10 tokens to every session and 80 once invoked, about $0.0001 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 commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
init
Initialize configurations for Supabase local development.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
handoff
Export a Waybill Bundle by default, or import one when requested.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.