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/test-module-namenpx skills add ncaq/konoka --skill test-module-namegit 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/test-module-name)<a href="https://agentmods.dev/skills/ncaq/konoka/test-module-name"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/test-module-name.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.00293 |
| Opus 5 | $0.00019 | $0.00147 |
| Sonnet 5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
test-module-name 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
テストモジュール名
Haskell/Cabalはライブラリのディレクトリとテストのディレクトリをはっきり分けるエコシステムのため、 ディレクトリは別々となります。
テストモジュールは一般的には分かり易さのため、
テストする対象のモジュールと同じ名前空間に置いて、
テストするモジュール名の末尾にSpecをつけてください。
つまりテスト対象のモジュール名がEnv.Typeの場合、
テストモジュール名はEnv.TypeSpecとなります。
モジュール名が同じ空間にあることで、 関係性が分かり易くなります。
もちろん、
- 狭い挙動を深く調べたいテストモジュール
- 複数のモジュールを深く利用するテストモジュール
- 特定のモジュールに依存しないテストモジュール
これらには適切なモジュール名をつける必要があります。
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 · 29 lines · 38 tokens per session scan A a3f10d11b3de
test-module-name is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 38 tokens to every session and 293 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-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
bun-test-lifecycle
Use for test lifecycle hooks: beforeAll, afterAll, beforeEach, afterEach, fixtures, preload.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
bun-test-basics
Use for bun:test syntax, assertions, describe/it, test.skip/only/each, and basic patterns.
bun-test-coverage
Use for test coverage with Bun, --coverage flag, lcov reports, thresholds, and CI integration.
tools-unity-test-framework
Unity Test Framework patterns for EditMode and PlayMode tests including async testing, mocking, and test organization.