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 ncaq/konoka --skill semantic-htmlgit clone --depth 1 https://github.com/ncaq/konokaWrote 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/ncaq/konoka/semantic-html)<a href="https://agentmods.dev/skills/ncaq/konoka/semantic-html"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/semantic-html/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/ncaq/konoka/semantic-html"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/semantic-html.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.00026 | $0.00744 |
| Opus 5 | $0.00013 | $0.00372 |
| Sonnet 5 | $0.00005 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
semantic-html 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 4d 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
セマンティックHTML
原則
意味のある構造には<div>ではなく、なるべくセマンティックHTML要素を使ってください。
<div>にコメントで意味を補足するぐらいなら、適切な要素を選ぶべきです。
セマンティック要素はアクセシビリティツール、LLM、人間のいずれにとっても読みやすくなります。
<div>はスタイリング目的のグルーピングなど、意味を持たないコンテナとしてのみ使います。
要素の使い分け
<main>
ページの主要コンテンツです。 1ページにつき1つだけ使います。
<main>
<h1>ページタイトル</h1>
<section>...</section>
<section>...</section>
</main>
<article>
独立して意味をなすコンテンツです。 ブログ記事、コメント、カードなどが該当します。
<article>
<h3>記事タイトル</h3>
<p>{content}</p>
</article>
<section>
見出し(<h1>-<h6>)を伴うコンテンツのまとまりに使います。
ページ内の各セクション、フォームのグループなどが該当します。
// Good
<section>
<h3>承認セクション</h3>
<textarea />
<button>承認</button>
</section>
// Bad
<div>
<h3>承認セクション</h3>
<textarea />
<button>承認</button>
</div>
<header>
セクションやページの導入部分です。 タイトル、ロゴ、ナビゲーションなどを含みます。
<header>
<h1>ページタイトル</h1>
<StatusBadge status={status} />
</header>
<footer>
セクションやページの末尾です。 関連リンク、アクションボタン群などを含みます。
<footer>
<button>キャンセル</button>
<button>保存</button>
</footer>
<nav>
主要なナビゲーションリンクのまとまりです。 サイドバーメニュー、パンくずリスト、ページ内リンクなどが該当します。
<nav>
<a href="/dashboard">ダッシュボード</a>
<a href="/settings">設定</a>
</nav>
<aside>
メインコンテンツに対する補足情報です。 サイドバー、注釈、関連リンクなどが該当します。
<aside>
<h4>関連情報</h4>
<ul>...</ul>
</aside>
<div>を使ってよい場合
- Flexbox/Gridなどレイアウト目的のラッパー
- スタイリングのためだけのグルーピング
- 上記のどのセマンティック要素にも該当しないコンテナ
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.
- 4d ago First seen · 118 lines · 26 tokens per session scan A b9af8e3fefa7
semantic-html is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 744 once invoked, about $0.0001 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-05.
Other skills, from other repositories
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG/App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker…
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
auto-animate
AutoAnimate (@formkit/auto-animate) zero-config animations for React. Use for list transitions, accordions, toasts, or encountering SSR errors, animation libraries complexity.
base-ui-react
MUI Base UI unstyled React components with Floating UI. Use for accessible components, Radix UI migration, render props API, or encountering positioning, popup, v1.0 rc / pre-GA issues.
bun-nextjs
This skill should be used when the user asks about "Next.js with Bun", "Bun and Next", "running Next.js on Bun", "Next.js development with Bun", "create-next-app with Bun", or building Next.js applications using Bun as the runtime.
bun-react-ssr
Use when building server-rendered React with Bun, including streaming SSR, hydration, renderToString, or custom SSR without a framework.