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 as-const-satisfiesgit 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/as-const-satisfies)<a href="https://agentmods.dev/skills/ncaq/konoka/as-const-satisfies"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/as-const-satisfies/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/as-const-satisfies"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/as-const-satisfies.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.00039 | $0.01413 |
| Opus 5 | $0.00019 | $0.00707 |
| Sonnet 5 | $0.00008 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
as-const-satisfies 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.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
as const satisfies パターンの使用
基本原則
定数定義ではas constを積極的に使用します。
as constによりリテラル型が保持され、
より厳密な型推論が可能になります。
名前のついている特定の型で型チェックも出来る場合はas const satisfies Typeを使用します。
これで「as constを使いたいが、型のチェックもしたい」という要求を満たせます。
使い分け
as constを使う場合
定数定義では基本的にas constを使います。
リテラル型の保持と型レベルでのreadonly(ただし実行時にはオブジェクトは凍結されません)が得られます。
const status = {
pending: "pending",
approved: "approved",
rejected: "rejected",
} as const;
// `status.pending`の型: "pending"
as const satisfies Typeを使う場合
as constの利点を保ちつつ型チェックも行いたい場合に使用します。
const status = {
pending: "pending",
approved: "approved",
rejected: "rejected",
} as const satisfies Record<string, string>;
// `status.pending`の型: "pending"(リテラル型保持)
// かつ`Record<string, string>`を満たすことが保証される
: Type や satisfies Type を使う場合
可変性が必要な場合や、 リテラル型の保持が問題になる場合に限り使用します。
// 可変な配列が必要な場合
const items: string[] = [];
items.push("a"); // OK
// `as const`だと`readonly`になり`push`できない
as const satisfiesがそのまま使えないパターン
satisfiesで指定する型が可変な型の場合、
as constのreadonly性と競合してエラーになることがあります。
問題のあるパターン
type Config = {
values: string[];
};
// エラー: `readonly string[]`は`string[]`に割り当てられない
const config = {
values: ["a", "b", "c"],
} as const satisfies Config;
解決方法: readonlyな型を定義する
satisfiesで使用する型自体をreadonlyにすることで解決できます。
type Config = {
readonly values: readonly string[];
};
const config = {
values: ["a", "b", "c"],
} as const satisfies Config;
// `config.values`の型: `readonly ["a", "b", "c"]`
Readonlyユーティリティ型の活用
既存の型をreadonly化する場合はReadonlyや再帰的なDeepReadonlyを使用できます。
type MutableConfig = {
values: string[];
nested: {
items: number[];
};
};
// 浅い`readonly`化
type ShallowReadonlyConfig = Readonly<MutableConfig>;
// 深い`readonly`化が必要な場合は自前で定義
// この定義はプレーンオブジェクトと配列のみを対象としています。
// Map/Set/Date等のビルトインオブジェクトを含む型には専用の対応が必要です。
type DeepReadonly<T> = T extends readonly (infer U)[]
? readonly DeepReadonly<U>[]
: T extends object
? { readonly [P in keyof T]: DeepReadonly<T[P]> }
: T;
type ReadonlyConfig = DeepReadonly<MutableConfig>;
const config = {
values: ["a", "b", "c"],
nested: {
items: [1, 2, 3],
},
} as const satisfies ReadonlyConfig;
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 · 176 lines · 39 tokens per session scan A 91935c7574a1
as-const-satisfies is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,413 once invoked, about $0.0002 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
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
bun-bundler
This skill should be used when the user asks about "bun build", "Bun.build", "bundling with Bun", "code splitting", "tree shaking", "minification", "sourcemaps", "bundle optimization", "esbuild alternative", "building for production", "bundling TypeScript", "bundling for browser", "bundling for Node", or…
bun-hot-reloading
Use when implementing hot reloading with Bun (--hot, --watch), HMR, or automatic code reloading during development. Covers watch mode, hot mode, and HTTP server reload.
language-typescript
TypeScript conventions with generic guidance plus a monorepo-specific addendum.
frontend-ai-guide
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
typescript-rules
React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.