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/azhi-ss/html-effectiveness/01-explorenpx skills add Azhi-ss/html-effectiveness --skill 01-exploregit clone --depth 1 https://github.com/Azhi-ss/html-effectivenessWrote 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/azhi-ss/html-effectiveness/01-explore)<a href="https://agentmods.dev/skills/azhi-ss/html-effectiveness/01-explore"><img src="https://agentmods.dev/badge/skills/azhi-ss/html-effectiveness/01-explore.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.00092 | $0.01865 |
| Opus 5 | $0.00046 | $0.00932 |
| Sonnet 5 | $0.00018 | $0.00373 |
| Haiku 4.5 | $0.00009 | $0.00186 |
Grade A, and why
html-effectiveness-explore 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
01-explore — 探索与规划
"You're not sure what you want yet. Ask the agent to fan out across several directions and lay them next to each other so you can point at one."
何时用
| 用户说 | 用哪个范式 | 模板 |
|---|---|---|
| "几种实现方式给我看看 / 哪种更好" | 三方案对比 | ../templates/compare.html |
| "compare X vs Y vs Z" | 同上 | 同上 |
| "我想要 UI 但说不清风格 / 几个方向给我看" | 视觉设计方向 | 自建(见下) |
| "做一份实现计划 / RFC / 怎么落地" | 实现计划 | ../templates/plan.html |
| "ship in 2 weeks 怎么排" | 同上 | 同上 |
范式 1.1 · 三方案对比
空间形状:每个方案 = 一个完整代码块 + 一张 Pro/Con 表 + 一行指标(bundle / 可测试性 / SSR / 复用)。三个方案要并排才能比较,markdown 只能上下堆。
最少要素:
- 至少 2、不超过 4 栏(多了用户记不住)
- 每栏一段最小可运行代码(5-15 行)
- Pro/Con 各 3 条,具体(不是 "easy to read",而是 "Single import reused across filter, command bar, and board search")
- 一行指标用同一组维度,便于横向比较
- 文末一段 agent 的推荐(不要让用户全自己判断)
HTML 骨架:
<div class="approaches">
<article class="approach">
<header><span class="tag">Approach 1</span><h2>Inline useEffect</h2></header>
<pre><code>...实际可运行代码...</code></pre>
<table class="proscons">
<thead><tr><th>Pro</th><th>Con</th></tr></thead>
<tbody><tr><td>...</td><td>...</td></tr></tbody>
</table>
<footer class="metrics">
<span>Bundle <b>+0 kb</b></span>
<span>Test <b>medium</b></span>
<span>Reuse <b>low</b></span>
<span>SSR <b>yes</b></span>
</footer>
</article>
<!-- 重复 2-3 次 -->
</div>
<aside class="recommendation"><strong>建议:</strong>...</aside>
关键 CSS:
.approaches { display: grid; grid-template-columns: repeat(3, 1fr); gap: 24px; }
.approach { display: flex; flex-direction: column; gap: 16px;
padding: 20px; border: 1px solid var(--gray-300);
border-radius: 12px; background: var(--white); }
.approach pre { flex: 1; max-height: 360px; overflow: auto; }
.proscons td:first-child { color: var(--success); }
.proscons td:last-child { color: var(--danger); }
.metrics { display: flex; gap: 16px; flex-wrap: wrap;
font-size: 13px; color: var(--gray-700); }
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 · 157 lines · 92 tokens per session scan A ed2adc22c9c3
html-effectiveness-explore is a skill published in the GitHub repository Azhi-ss/html-effectiveness (5 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 1,865 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
cinematic-scroll
Build cinematic scroll-driven, 3D-tilt, parallax, and environment-morphing websites — pinned chapter reveals, hero parallax, depth-image figures, hover-tilt cards, background-morphing layouts, release/launch pages, product story pages, or editorial commerce microsites. From a single self-contained scroll section (Mode…
cinematic-scroll
Build cinematic, scroll-driven websites — pinned chapter reveals, multi-depth parallax, 3D tilt, and environment-morphing backgrounds, from a single self-contained HTML section to a full Next.js release site. The motion grammar is the constant; the aesthetic is always the user's.
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
命理解读师
Skill "命理解读师" from learnwithu/mingli-master, covering 命理解读师 v2, 核心原则, 禁忌, 依赖 and 工作流程.
nopua
The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行').…
os-check-work
ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against…