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/ncaq/konoka/comparison-operatornpx skills add ncaq/konoka --skill comparison-operatorgit 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/comparison-operator)<a href="https://agentmods.dev/skills/ncaq/konoka/comparison-operator"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/comparison-operator.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.00038 | $0.00321 |
| Opus 5 | $0.00019 | $0.00161 |
| Sonnet 5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
comparison-operator 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 5d 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
比較演算子の向き
比較を書く時は、
x > yの形式よりx < yの形式を優先してください。
<や<=を使い、
左から右に向かって値が大きくなるように書きます。
頭の中の数直線上に数字を左から右へ並べて考えるため、 左の方が大きいと違和感を覚えるからです。
特に範囲チェックでは、 下限と上限を数直線の並び順に書けるため読みやすくなります。
// 好ましい
if (min <= x && x <= max)
// 避ける
if (x >= min && x <= max)
例外
このルールにそこまで執着はしません。
特に理由がなければ<や<=を好むという程度の優先度です。
その時書いている言語で広く普及しているリンターが、 変数を右に書くのをヨーダ記法として拒否する場合などは、 わざわざ逆らわずリンターに従ってください。
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.
- 5d ago First seen · 36 lines · 38 tokens per session scan A e9b49fc90cfe
comparison-operator is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 321 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-08-31.
Other skills, from other repositories
cloudflare-email-routing
Cloudflare Email Routing for receiving/sending emails via Workers. Use for email workers, forwarding, allowlists, or encountering Email Trigger errors, worker call failures, SPF issues.
bun-sqlite
Use for bun:sqlite, SQLite operations, prepared statements, transactions, and queries.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-http-server
Use when building HTTP servers with Bun.serve, handling requests/responses, implementing routing, creating REST APIs, or configuring fetch handlers.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.
cloudflare-workers-migration
Migrate to Cloudflare Workers from AWS Lambda, Vercel, Express, and Node.js. Use when porting existing applications to the edge, adapting serverless functions, or resolving Node.js API compatibility issues.