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 hirogoing/gradio-mini-agent --skill suspense-short-dramagit clone --depth 1 https://github.com/hirogoing/gradio-mini-agentWrote 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/hirogoing/gradio-mini-agent/suspense-short-drama)<a href="https://agentmods.dev/skills/hirogoing/gradio-mini-agent/suspense-short-drama"><img src="https://agentmods.dev/badge/skills/hirogoing/gradio-mini-agent/suspense-short-drama/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/hirogoing/gradio-mini-agent/suspense-short-drama"><img src="https://agentmods.dev/badge/skills/hirogoing/gradio-mini-agent/suspense-short-drama.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.00105 | $0.01138 |
| Opus 5 | $0.00053 | $0.00569 |
| Sonnet 5 | $0.00021 | $0.00228 |
| Haiku 4.5 | $0.00011 | $0.00114 |
Grade A, and why
suspense-short-drama 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 12d 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.
What it actually says
悬疑短剧剧本生成
核心工作流
- 需求确认 → 2. 世界观与人物设定 → 3. 分集大纲 → 4. 逐集剧本生成 → 5. 整体润色
Step 1: 需求确认
用户需提供：
- 主题：核心悬疑事件/谜题
- 集数：1-30集（每集约1000字）
- 可选：主要人物设定、特殊场景需求
Step 2: 世界观与人物设定
人物动机分析框架（见 references/人物动机分析.md）
为每个主要角色创建：
- 表层动机：角色公开追求的目标
- 深层动机：角色内心的真实渴望/恐惧
- 隐藏秘密：角色不愿公开的秘密
- 人物弧光：角色在剧集中的成长/变化
B 故事线设计（见 references/B故事线设计.md）
每部短剧需包含：
- A 故事线：主线悬疑谜题
- B 故事线：情感/关系副线（爱情、友情、亲情）
- B 故事与 A 故事的交织点：两条线索的交汇处
Step 3: 分集大纲
悬疑短剧结构模板
| 集数 | 类型 | 内容 | 钩子/悬念 |
|---|---|---|---|
| 第1集 | 建置 | 引入主要人物，建立世界观，抛出核心悬疑 | 核心谜题/危机出现 |
| 第2-n集 | 对抗 | 主角追查谜题，遭遇障碍，线索与反转 | 每集结尾悬念 |
| 倒数第2集 | 逼近真相 | 所有线索汇聚，真相浮现 | 惊人反转 |
| 大结局 | 解决 | 谜题揭晓，情感升华 | 余韵/彩蛋 |
悬念设置技巧（见 references/悬念设置技巧.md）
每集必须包含至少一种：
- 情节悬念：关键信息延迟揭示
- 人物悬念：角色身份/动机未知
- 氛围悬念：危险/恐怖氛围营造
- 信息悬念：观众知道但角色不知道
Step 4: 逐集剧本生成
剧本格式规范
【第X集】标题（可选）
【场景X】时间 - 地点
【场景类型】：内/外 日/夜
[动作描述：对白以外的画面内容，用现在时态]
---
人物A：（情绪指示）对白内容
人物B：对白内容
---
[动作/反应]
每集要素（约1000字）
- 开篇钩子（50-100字）：承接上集悬念，引入新冲突
- 核心情节（600-700字）：本集主要事件，对话与动作交织
- 结尾悬念（50-100字）：留下未解之谜或揭示惊人信息
- 情感线：至少一个角色的情感表达
反转剧情设计（见 references/反转剧情设计.md）
每3-4集安排一次剧情反转，包括：
- 人物反转：看似好人实为幕后黑手
- 信息反转：已知的"事实"被证伪
- 关系反转：角色间关系发生戏剧性变化
- 动机反转：真正动机与表面动机相反
Step 5: 整体润色
- 检查各集之间的逻辑连贯性
- 确认悬念的铺设与回收
- 验证人物动机的合理性
- 确保 B 故事线有发展有结局
参考资料
详见 references/ 目录：
人物动机分析.md- 角色深层次心理分析框架B故事线设计.md- 副线剧情设计方法论悬念设置技巧.md- 悬疑剧情核心技巧反转剧情设计.md- 剧情反转设计模式
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.
- 12d ago First seen · 104 lines · 105 tokens per session scan A 5133d6ff5108
suspense-short-drama is a skill published in the GitHub repository hirogoing/gradio-mini-agent (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 1,138 once invoked, about $0.0005 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.
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…