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 skills add glebis/claude-skills --skill weekly-digestgit clone --depth 1 https://github.com/glebis/claude-skillsWrote 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/glebis/claude-skills/weekly-digest)<a href="https://agentmods.dev/skills/glebis/claude-skills/weekly-digest"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/weekly-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/skills/glebis/claude-skills/weekly-digest"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/weekly-digest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 239 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00181 | $0.03930 |
| Opus 5 | $0.00090 | $0.01965 |
| Sonnet 5 | $0.00036 | $0.00786 |
| Haiku 4.5 | $0.00018 | $0.00393 |
Grade A, and why
weekly-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 8d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Digest
A research-to-publication pipeline that produces a scored, source-verified industry digest. The workflow has seven phases: init, scoping, research, verification, scoring, output, and presentation.
Phase 0: Init
Read ~/.claude/skills/weekly-digest/settings.json. Two possible states:
State A — file missing, or subjects is empty and file has no version field (fresh install): Run onboarding using the AskUserQuestion tool to collect all setup inputs in a single structured prompt:
AskUserQuestion({
questions: [
{
question: "What topic do you want to track weekly?",
header: "Topic",
options: [
{ label: "Agent orchestration", description: "Multi-agent frameworks, enterprise deployments, governance" },
{ label: "Design innovation", description: "Design tools, AI-design convergence, award-winning products" },
{ label: "Climate tech", description: "Clean energy, carbon capture, sustainability startups" },
{ label: "AI regulation", description: "EU AI Act, governance frameworks, copyright disputes" }
],
multiSelect: false
},
{
question: "Any geographic focus for sources?",
header: "Geography",
options: [
{ label: "Global (no filter)", description: "Include sources from all regions" },
{ label: "Europe, UK, Asia — not US", description: "Deprioritize American sources" },
{ label: "Europe only", description: "EU and UK sources preferred" },
{ label: "Asia-Pacific", description: "Japan, Korea, China, Singapore, India, Australia" }
],
multiSelect: false
},
{
question: "How many top items should the digest include?",
header: "Digest size",
options: [
{ label: "5 items (Recommended)", description: "Good balance of depth and brevity" },
{ label: "3 items", description: "Quick scan, only the best" },
{ label: "10 items", description: "Comprehensive coverage" }
],
multiSelect: false
},
{
question: "Where should output files go?",
header: "Output",
options: [
{ label: "output/ (Recommended)", description: "Relative to current working directory" },
{ label: "~/Digests/", description: "Home directory, shared across projects" }
],
multiSelect: false
}
]
})
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 325 lines · 181 tokens per session scan A 21ee22de3a4e
weekly-digest is a skill published in the GitHub repository glebis/claude-skills (375 stars, last pushed 10d ago), licensed MIT. It adds 181 tokens to every session and 3,930 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…