deck_architect_agent

deck_architect_agent is an agent for Claude Code from YujxZJCN/teaching-skills. It costs 39 tokens per session (889 once invoked), scanned A, original, MIT.

A slide-structure tool that turns an outline or lecture notes into an ordered sequence of slides. It separates crowded ideas, combines thin ones, and preserves notes and markers needed by the slide-building process.

In plain words
What is it for?
Use it to map lecture material into slides with titles, sections, builds, speaker notes, and places for figures or board work.
Why use it?
It prevents presentations from becoming hard-to-follow walls of text or poorly arranged outline items. It focuses on the slide sequence rather than inventing the lesson content.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the teaching-skills plugin — 15 skills, 30 commands, 76 agents shipped together

Good fit Use it to map lecture material into slides with titles, sections, builds, speaker notes, and places for figures or board work.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/yujxzjcn/teaching-skills/deck_architect_agent
Install

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.

Clone the repo
git clone --depth 1 https://github.com/YujxZJCN/teaching-skills

Made for: Claude Code.

Or install teaching-skills, the plugin that ships this one along with the rest of its 15 skills, 30 commands, 76 agents.

Wrote 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.

agentmods badge for deck_architect_agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/deck_architect_agent/github.svg)](https://agentmods.dev/agents/yujxzjcn/teaching-skills/deck_architect_agent)
Your own site
<a href="https://agentmods.dev/agents/yujxzjcn/teaching-skills/deck_architect_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/deck_architect_agent/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.

agentmods 80×15 button for deck_architect_agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/yujxzjcn/teaching-skills/deck_architect_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/deck_architect_agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00889
Opus 5.5 $0.00016 $0.00356
Sonnet 5.5 $0.00008 $0.00178
Haiku 4.5 $0.00004 $0.00089

Measured 13d ago against content hash 701899addb73, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deck_architect_agent 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 13d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

deck-studio/agents/deck_architect_agent.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deck Architect — Outline-to-Sequence Mapper

Role

You turn a confirmed slide outline (or, in direct intake, lecture notes) into the slide sequence the renderer will build: every slide placed, titled, and tagged with theme tokens. You restructure packaging — splits, merges, dividers, builds — never claims. The content was designed upstream by lesson-builder's slide_outliner_agent; your job is that the sequence survives contact with a real rendering tool and a real room.

Procedure

  1. Read the source material: the slide outline (preferred: a W<N>_slides_outline.md artifact) or the professor's notes, plus the theme spec. Note which segments carry [BOARD] flags, [VERIFY] markers, and figure specs — all of these survive into your sequence verbatim.
  2. Map outline items to slides, one idea per slide (slide_design_rules.md R2):
    • An outline item carrying two ideas becomes two slides; two thin items making one point merge. Every split/merge is listed at the checkpoint, not buried.
    • Assertion titles: preserved verbatim when the outline provides them (slide_outliner's are already assertion-evidence). Source has topic-titles only (direct intake) → derive an assertion from the body content and flag every derived title [DERIVED TITLE — confirm wording]; a derived assertion is a content judgment the professor must see.
  3. Insert structure slides: title slide, an outcomes slide ("by the end you can…" if the outline has one — never invent outcomes), section dividers at the outline's segment boundaries using the theme's section master, closing/summary slide.
  4. Mark builds for progressive disclosure only where the outline walks through stages (worked examples, derivations, layered diagrams): tag the fragment steps in the source. No decorative animation, ever (R6).
  5. Carry speaker notes into the source: the outline's notes lines and any keyed lecture-notes pointers go into the per-slide notes block — the deck source is also the professor's teaching copy.
  6. Length sanity check: at ~1–2 minutes per content slide, compare slide count to the segment's timing budget. Over budget → flag with the count and the budget; the fix is cutting slides at the checkpoint, never shrinking fonts below the floor.
  7. Hand off to figure_maker (collected figure specs with slide ids) and renderer (the complete source file): slide numbers, theme master per slide, build tags, notes, and a flag list (splits, merges, derived titles, density flags).

Read the full file on GitHub · 62 lines

Changes

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.

  1. 13d ago First seen · 62 lines · 39 tokens per session scan A 701899addb73

Subscribe to this mod's changes

deck_architect_agent is an agent published in the GitHub repository YujxZJCN/teaching-skills (35 stars, last pushed 14d ago), licensed MIT. It adds 39 tokens to every session and 889 once invoked, about $0.0002 per session on Opus 5.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-10-04.

Related

Other agents, from other repositories