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 jscraik/Agent-Skills --skill talk-scheire-artificial-intelligencegit clone --depth 1 https://github.com/jscraik/Agent-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/jscraik/agent-skills/talk-scheire-artificial-intelligence)<a href="https://agentmods.dev/skills/jscraik/agent-skills/talk-scheire-artificial-intelligence"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/talk-scheire-artificial-intelligence/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/jscraik/agent-skills/talk-scheire-artificial-intelligence"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/talk-scheire-artificial-intelligence.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.00174 | $0.01440 |
| Opus 5 | $0.00087 | $0.00720 |
| Sonnet 5 | $0.00035 | $0.00288 |
| Haiku 4.5 | $0.00017 | $0.00144 |
Grade A, and why
talk-scheire-artificial-intelligence 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artificial Intelligence — Lieven Scheire
A keynote by Belgian physicist, comedian and science communicator Lieven Scheire that demystifies AI for a developer audience. His central thesis: AI is "a new kind of software that is good at pattern recognition" — not magic, not (yet) thinking — and that single capability, unlocked by enough compute and data, is what kicked off the current AI revolution.
Grounding rules — MUST follow when answering
- Before answering any specific question, read
outline.mdto locate the relevant section, then read that section oftranscript.md. - When attributing words, quote short, non-sensitive excerpts from
transcript.md. Never put quotation marks around paraphrased content. - If a claim isn't in
transcript.md, say "the talk doesn't address this" — do not infer positions from outside knowledge. - Cite by transcript line range or section heading whenever possible.
- Speaker attribution is unreliable for this transcript — the source has no per-speaker labels and contains speech-to-text artifacts (e.g. "she's always hard" likely = "Scheire is always hard", "dodge" likely = "Dutch", "wearer's only" likely = "Where's Wally"). The vast majority of the talk is Scheire speaking; a brief intro segment is by an unnamed host/MC. Prefer phrasing like "Scheire said..." for the main content. For the opening intro lines, use "the host said..." or "in the introduction...".
- Preserve transcription artifacts when quoting verbatim — do not silently "correct" them. If a garbled phrase is obviously a transcription error (e.g. "wearer's only robot" = "Where's Wally robot"), you may note the likely intended phrase in square brackets after the safe excerpts.
General lookup procedure
Apply these steps for every request about the talk's content:
- Read
outline.mdto locate the relevant section(s). - Read the matching range of
transcript.md. - Answer using safe excerpts from
transcript.md. Do not paraphrase Scheire's words while presenting them as a quote. - Cite line numbers or section headings so the user can verify.
- If the answer genuinely isn't in the transcript, say so explicitly — do not reach for outside knowledge to fill the gap unless the user explicitly asks (and then mark that part clearly as "not from the talk").
What ships with it
4 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 · 75 lines · 174 tokens per session scan A 06a18140686c
talk-scheire-artificial-intelligence is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 174 tokens to every session and 1,440 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
ai-expertise-interrogation-designer
Design a Funhouse Mirror activity where students use their own domain expertise to detect AI distortions, omissions, and overconfidence. Use when students know a subject well enough to evaluate AI claims about it.
disciplinary-ai-literacy-sequence-designer
Design a sequence where students compare AI's handling of the same question across disciplines, developing a mental model of where AI is reliable vs. distorting based on knowledge type.
prompt-literacy-sequence-designer
Design a learning sequence teaching prompt quality — comparing vague vs. refined prompts to show why specificity and context transform AI output. Use when students use AI without understanding why output quality varies.
chain-llm-pattern
Build multi-step LLM reasoning chains in n8n using Groq, OpenAI, or Claude for structured data extraction, categorization, scoring, and analysis. Use this skill whenever the user wants to chain multiple LLM calls together in an n8n workflow — phrases like "extract entities then categorize", "multi-step LLM prompt"…
jupyter-notebook
Use when the user asks to create, scaffold, or edit Jupyter notebooks (.ipynb) for experiments, explorations, or tutorials; prefer the bundled templates and run the helper script newnotebook.py to generate a clean starting notebook.
数据流编程
A programming style that represents software as a graph of data transformations, where each step passes data to the next.