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/function-resultnpx skills add ncaq/konoka --skill function-resultgit clone --depth 1 https://github.com/ncaq/konokaWhat 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.00051 | $0.00347 |
| Opus 5 | $0.00026 | $0.00173 |
| Sonnet 5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
function-result 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 2d 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
関数の最後の値は捨てない
関数の最後で、
return ()pure ()void
などを使って値を捨てないでください。
特に理由がないならば関数が値を返すように型の方を合わせてください。
その時その関数の返り値が別に必要ない場合でも、 呼び出し側で捨てれば多くは問題ない話です。 呼び出し側で捨てる手間は非常に少ないです。
必要になった場合に使える余地を残しておいたほうが後々必要になった時に大きく書き換えなくて済みます。
関数の最後がwriteFileのような、
MonadIO m => m ()のようにユニットを返す関数であれば、
自然とそのまま返り値をMonadIO m => m ()にして問題ありません。
ちょっとした補助関数を最後に呼び出して、 それの返り値を返してしまうと、 関数全体の挙動が誤解されてしまうような場合のみ、 最後の値を捨てることを検討してください。
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.
- 2d ago First seen · 33 lines · 51 tokens per session scan A 6642491dbc07
function-result is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 51 tokens to every session and 347 once invoked, about $0.0003 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
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
plano-agent-orchestration
Improve multi-agent orchestration in Plano. Use for agent registration, agent listener wiring, and capability-focused agent descriptions for accurate routing.
plano-filter-guardrails
Harden Plano filter chains and guardrails. Use for MCP filter setup, prompt guard responses, and safe filter ordering.
veo-3.2-prompter
Expert prompt engineering for Google Veo 3.2 (Artemis engine). Use when the user wants to generate a video with Veo 3.2, needs help crafting cinematic prompts, or mentions Veo, Google video generation, or Artemis engine.
ads-linkedin
Audit LinkedIn Ads measurement, Insight Tag and conversions, professional audiences, lead generation, ABM, creative, bidding, budgets, pacing, automation, and policy. Use for LinkedIn Ads, Campaign Manager, Insight Tag, Lead Gen Forms, Thought Leader Ads, ABM campaigns, or B2B paid media.
military-commander
上将军·运筹帷幄 - 以兵法之道统筹全局，运筹帷幄之中，决胜千里之外，集中优势兵力打歼灭战.