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 aria-usagegit 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/aria-usage)<a href="https://agentmods.dev/skills/ncaq/konoka/aria-usage"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/aria-usage/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/aria-usage"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/aria-usage.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.00040 | $0.01921 |
| Opus 5.5 | $0.00016 | $0.00768 |
| Sonnet 5.5 | $0.00008 | $0.00384 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
aria-usage 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WAI-ARIAの使用指針
無意味で冗長なARIA属性の追加を避けてください。
この文書は以下の著作物の内容を要約・改変して作成しています。
- role属性とは、aria-*属性とは、WAI-ARIAとは、いったい何なのか、いつ使うべきなのか
- ARIA in HTML (Copyright © W3C)
- HTML Accessibility API Mappings 1.0 (Copyright © W3C)
- WAI-ARIA Authoring Practices Guide (Copyright © W3C, W3C Software and Document License)
暗黙のWAI-ARIAセマンティクス
HTMLの要素は暗黙のWAI-ARIAセマンティクスを持っています。
role属性やaria-*属性を書かなくても、
明示的に書いたのと同じ状態になっています。
たとえば<button>要素は、
WAI-ARIAの属性がなくても「ボタン」というロールと、
テキストコンテンツによる名前を持ちます。
<!-- この2つは同じセマンティクスです。下のように書く必要はありません -->
<button>送信</button>
<button role="button" aria-label="送信">送信</button>
HTMLの要素や属性をそれらの目的通りに使っていれば、 適切な暗黙のWAI-ARIAセマンティクスが自動的に付与されます。 暗黙のセマンティクスの詳細は、 HTML Accessibility API Mappings 1.0 に定義されています。
WAI-ARIAセマンティクスとHTMLのコンフリクト
WAI-ARIAの属性はHTMLの暗黙のセマンティクスを上書きします。 誤った属性値を使ってしまうとアクセシビリティを下げてしまいます。 しかも通常の動作確認ではその誤りに気付けません。
<!-- h1要素は暗黙のうちにaria-level="1"を持つが、
aria-level属性が明示的に指定されたことで見出しレベル2に変更されている -->
<h1 aria-level="2">これは見出しレベル2です</h1>
一方でchecked属性のような「強いネイティブセマンティクス」はWAI-ARIAの属性値を無視します。
<!-- aria-checkedは無視され、HTMLネイティブのchecked属性値のみが支援技術に提示される -->
<label>
<input type="checkbox" checked="checked" aria-checked="false" />
このチェックボックスは、チェックされているでしょうか?
</label>
No ARIA is better than Bad ARIA
APGのRead Me Firstにある通り、 悪いARIAよりもARIA無しのほうが良いです。 この原則を理解するために、 2つの重要な考え方があります。
ロールは約束である
<div role="button">Place Order</div>
role="button"を指定した以上、
この要素はボタンとして完璧に振る舞わなければなりません。
クリックだけでなく、
キーボードでフォーカスできてSpaceキーやEnterキーでも操作できる必要があります。
ロールを指定するということは
「このロールに期待されることは、この要素がすべて満たしています」
というユーザーに対する約束です。
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 · 151 lines · 40 tokens per session scan A 6d00c175fb4d
aria-usage is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 1,921 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-09-05.
Other skills, from other repositories
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.
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.
design-tokens
This skill should be used when a user wants to scaffold or refactor a design token system — e.g. "set up design tokens", "create a design system foundation", "extract these hardcoded colors into tokens", "add a type scale", "theming setup", or "dark mode tokens". It produces a single source of truth for color, type…
accessibility-audit
This skill should be used when evaluating a design, page, or component against accessibility standards and producing a severity-scored report. Trigger phrases include "audit accessibility", "check a11y", "is this accessible", "WCAG audit", "check color contrast", and "accessibility review before handoff". Use it to…
accessibility
Audits code for WCAG 2.2 AA compliance and provides design guidance for accessible components. Covers semantic HTML, ARIA, keyboard nav, contrast, focus management, and motion.
accessible-components
This skill should be used when the user wants to build or fix accessible UI components or set up accessibility tooling — triggers like "make this modal accessible", "build an accessible dropdown", "add ARIA to this", "accessible tabs/combobox/tooltip/accordion", "set up a11y linting", or "fix keyboard navigation". It…