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/veigap/talksmith/ingestnpx skills add veigap/talksmith --skill ingestgit clone --depth 1 https://github.com/veigap/talksmithWrote 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/veigap/talksmith/ingest)<a href="https://agentmods.dev/skills/veigap/talksmith/ingest"><img src="https://agentmods.dev/badge/skills/veigap/talksmith/ingest.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.00074 | $0.01433 |
| Opus 5 | $0.00037 | $0.00717 |
| Sonnet 5 | $0.00015 | $0.00287 |
| Haiku 4.5 | $0.00007 | $0.00143 |
Grade A, and why
talksmith:ingest 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
talksmith:ingest — Capture a web page as Talk research
This skill downloads one web page and stores it under the active Talk's research/web/<folder-name>/ so the librarian picks it up in Step 3 (Corpus) alongside articles and chat exports.
The actual fetch is performed by fetch.py — a stdlib-only Python script (no requests, no beautifulsoup4, no external deps). The skill is the orchestration wrapper: it locates the active Talk, runs the script, surfaces errors back to the orchestrator.
When to use
- Presenter mentions a URL during Collect (Step 2) and wants its content captured.
- Presenter realizes mid-Draft that a referenced URL would back a slide and the page isn't yet in the knowledge base.
- New sources arrive after Step 3 has already run — invoke
ingestfor each URL, then perform the Librarian role to add the new web folder to the corpus.
Inputs
| Input | Required? | Source |
|---|---|---|
url |
yes | Presenter (free-text — there's no useful context to propose candidates from). Must be http:// or https://. |
talk_path |
yes | The orchestrator (active Talk path, e.g. talks/gen-models-bio/). |
folder_name |
optional | Defaults to a slugified <URL-host>-<first-path-segment> — see fetch.py _default_folder_name + _slugify for the canonical definition (lowercase, non-alphanumeric → -, 80-char cap). Override when the presenter wants a more meaningful name (e.g. transformer-paper-google instead of arxiv-org-abs). |
Output
talks/<Talk>/research/web/<folder-name>/
├── metadata.yaml # url, fetched_at (UTC ISO 8601), title, http_status, byte_size, asset manifest
├── original.html # raw fetched HTML — the source of truth (preserved verbatim)
├── page.md # best-effort HTML → Markdown extraction (headings, paragraphs, lists, links, code, images)
└── assets/ # best-effort image downloads (only when at least one image was reachable; folder removed if empty)
What ships with it
1 file 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.
- 3d ago First seen · 81 lines · 74 tokens per session scan A 6ea60bb7ed6a
talksmith:ingest is a skill published in the GitHub repository veigap/talksmith (10 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 1,433 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…