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.
git clone --depth 1 https://github.com/KumihoIO/kumiho-pluginsWrote 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/commands/kumihoio/kumiho-plugins/kumiho-personalize)<a href="https://agentmods.dev/commands/kumihoio/kumiho-plugins/kumiho-personalize"><img src="https://agentmods.dev/badge/commands/kumihoio/kumiho-plugins/kumiho-personalize/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/commands/kumihoio/kumiho-plugins/kumiho-personalize"><img src="https://agentmods.dev/badge/commands/kumihoio/kumiho-plugins/kumiho-personalize.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.00019 | $0.00858 |
| Opus 5 | $0.00010 | $0.00429 |
| Sonnet 5 | $0.00004 | $0.00172 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
kumiho-personalize 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 11d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kumiho Personalize
Update the CognitiveMemory/agent.instruction item with new preferences.
Creates a new revision and moves the published tag — old preferences are
preserved in revision history.
Steps
-
Load current preferences — fetch the current published revision:
kumiho_get_revision_by_tag( item_kref = "kref://CognitiveMemory/agent.instruction", tag = "published" )If that returns not-found, retry once with the space-qualified kref — self-hosted CE servers do not resolve the space-less shorthand:
kumiho_get_revision_by_tag( item_kref = "kref://CognitiveMemory/personal/agent.instruction", tag = "published" )Use whichever kref resolved for all subsequent steps.
If the item doesn't exist at either kref, tell the user: "No identity found yet — start a new session and I'll walk you through the full onboarding." Then stop.
Parse the metadata fields from the current revision so you can show the user what's currently set.
-
Show current settings and ask what to change — display the current values in a compact table and ask the user what they'd like to update. Let them change one field or many. The fields are:
Field Description agent_nameWhat the agent calls itself user_nameWhat the agent calls the user user_languagesPreferred languages (e.g. "English, Korean") communication_tonecasual / professional / balanced verbosityconcise / balanced / detailed user_roleUser's role or area of expertise user_expertise_levelbeginner / intermediate / advanced primary_toolsTools/technologies the user works with artifact_dirWhere to save conversation artifacts timezoneUser's timezone interaction_rulesCustom behavior rules memory_behaviourHow aggressively to remember (minimal / balanced / thorough)
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.
- 11d ago First seen · 99 lines · 19 tokens per session scan A 0ca6a3e9110b
kumiho-personalize is a command published in the GitHub repository KumihoIO/kumiho-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 858 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.