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.
/plugin marketplace add Linaqruf/kana-code-pluginsnpx agentmods add plugins/linaqruf/kana-code-plugins/kana-code-rpcgit clone --depth 1 https://github.com/Linaqruf/kana-code-pluginsGrade A, and why
kana-code-rpc 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 yesterday.
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
{
"name": "kana-code-rpc",
"displayName": "Kana Code RPC",
"version": "1.0.0",
"description": "Display Claude Code activity as Discord Rich Presence. Shows project name, current activity (tool use, thinking, compacting, waiting), model, context usage, cost, git branch, lines changed, agent name, and a repository link button — with PID-based multi-session daemon support.",
"author": {
"name": "Linaqruf"
},
"license": "MIT",
"repository": "https://github.com/Linaqruf/kana-code-plugins",
"keywords": ["discord", "rich-presence", "activity", "status", "daemon", "hooks", "tokens", "cost", "multi-session"]
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 13 lines scan A 7a7253acbad7
kana-code-rpc is a plugin published in the GitHub repository Linaqruf/kana-code-plugins (4 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
knowledge-patch
Offline monoplugin that routes three native skills to bundled technology patches through compact generated catalogs.
nevaberry
Public marketplace for Nevaberry plugins.
marcel-bich-claude-marketplace
Plugin marketplace listing 8 plugins: credo, dogma, signal, limit, hydra.
credo
The mentor framework for Claude Code: a self-contained process layer with per-session modes, a work-item lifecycle with a hard Definition of Done, budget-aware autonomy, visual verification, and safety rules that travel into every subagent.
get-shit-done
Installer for the Get-Shit-Done workflow system (own secured & frozen fork, markdown skills only) - meta-prompting, context engineering and spec-driven development.
dogma
Intelligent sync of Claude instructions with enforcement hooks for security and consistency.