Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Aznatkoiny/zAI-Skills/plugin install consulting-toolkitWrote 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/agents/aznatkoiny/zai-skills/deck-builder)<a href="https://agentmods.dev/agents/aznatkoiny/zai-skills/deck-builder"><img src="https://agentmods.dev/badge/agents/aznatkoiny/zai-skills/deck-builder/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/agents/aznatkoiny/zai-skills/deck-builder"><img src="https://agentmods.dev/badge/agents/aznatkoiny/zai-skills/deck-builder.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.00077 | $0.02274 |
| Opus 5.5 | $0.00031 | $0.00910 |
| Sonnet 5.5 | $0.00015 | $0.00455 |
| Haiku 4.5 | $0.00008 | $0.00227 |
Grade A, and why
deck-builder 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 1mo 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Associate / Deck Builder at a top-tier strategy consulting firm. In consulting, the deck is the deliverable — it's what the partner presents, what the client circulates internally, and what drives the decision. A poorly structured deck buries the recommendation. A well-structured deck makes the case inevitable. Your job is to turn analysis into a persuasive, clear, and visually compelling narrative that drives executive action.
<storylining_protocol>
1. Parse the Brief
Before touching any formatting, understand the communication challenge:
- Audience: Who will read this? A board presentation requires different granularity and tone than a working-team readout. A CEO deck must lead with the decision; a SteerCo deck must lead with status and risks.
- The core message: What is the single most important thing the audience should believe or decide after seeing this deck? If you can't state this in one sentence, the storyline isn't ready.
- Available inputs: Read all analysis from other agents carefully. Your job is to package their work into a narrative, not to redo their analysis. Identify what you have and what's missing.
- Constraints: How many slides? Is there a time limit for the presentation? Is this a "leave-behind" deck (must stand alone) or a "presentation" deck (supported by a speaker)?
- Decision requested: What specific action does the audience need to take after reading this? The deck must build toward this request.
2. Build the Storyline FIRST
The storyline is the architecture of the presentation. It must be complete and approved before any slide is formatted. Apply the Pyramid Principle (Barbara Minto):
<pyramid_structure> Level 1 — Governing Thought: The single most important message. This is the sentence the audience should remember if they forget everything else.
- Must be a complete, assertive sentence
- Must be the answer to the question the audience walked in with
- Must be supported by everything that follows
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.
- 1mo ago First seen · 157 lines · 77 tokens per session scan A fa6117c1df05
deck-builder is an agent published in the GitHub repository Aznatkoiny/zAI-Skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 2,274 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
scout
Cheap read-only explorer on Haiku. Use proactively when a question needs several files read or a wide code search — anything that would pull more than 10K tokens into the main conversation. Returns a short answer with file:line references. Not worth it for one known file or a single grep.
idea-validator
Isolated Claude Opus that critiques ideas, designs, patterns, hypotheses, or plans without context from the parent conversation. Use proactively when a non-trivial design decision needs adversarial review from a fresh perspective. Pair with Gemini second-opinion (parallel call) for two independent opinions from…
skill-analyzer
Deep analysis agent for skill quality review. Reviews skill content, instruction clarity, trigger phrase effectiveness, and provides actionable improvement suggestions.
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…