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 skills add howdeploy/kisa-stack --skill shojiwmgit clone --depth 1 https://github.com/howdeploy/kisa-stackWrote 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/howdeploy/kisa-stack/shojiwm)<a href="https://agentmods.dev/skills/howdeploy/kisa-stack/shojiwm"><img src="https://agentmods.dev/badge/skills/howdeploy/kisa-stack/shojiwm/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/skills/howdeploy/kisa-stack/shojiwm"><img src="https://agentmods.dev/badge/skills/howdeploy/kisa-stack/shojiwm.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.00050 | $0.00949 |
| Opus 5.5 | $0.00020 | $0.00380 |
| Sonnet 5.5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
shojiwm 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KISA ShojiWM desktop
Locate the user's installed config and/or the howdeploy/kisa-stack checkout
before changing files. Public reference:
https://github.com/howdeploy/kisa-stack/tree/main/dotfiles . Read its README.md,
AGENTS.md, sources.json and the docs relevant to the request. This skill does
not require the author's filesystem, Wiki, accounts or other installed skills.
Source map
Installed files are under ${XDG_CONFIG_HOME:-$HOME/.config}; published sources
are under dotfiles/config/ in kisa-stack. Installation copies them, rather than
linking live state into Git.
| Concern | Relative path under the config root |
|---|---|
| Composition, effects, bindings, outputs, processes, IPC | shojiwm/src/index.tsx |
| Tiling, floating, focus, workspaces, geometry, minimize/fullscreen | shojiwm/src/window-manager.ts |
| Compositor shader modules and GLSL | shojiwm/src/effect/ |
| Shell entry, top panel/dock/tray | shoji-shell/shell.qml, ScreenShell.qml, Dock.qml |
| Palette and opt-in gates | shoji-shell/Theme.qml, Settings.qml |
| Wallpaper and widget sets | Wallpapers.qml, WidgetLayouts.qml, WallpaperPicker.qml under shoji-shell/ |
| Widget transition lifetime | WidgetWaveLoader.qml, WidgetWaveSnapshot.qml, WidgetWaveMask.qml |
| Launcher data and appearance | walker/favorites.toml, walker/themes/shoji/, elephant/ |
Compositor contract
The pinned fork is https://github.com/howdeploy/ShojiWM on main,
revision recorded in dotfiles/sources.json. Fork main is the integration
branch. Contributions include keyboard layout status/LEDs, cursor scaling,
full-window subsurfaces and native workspace waves; dotfiles/docs/fork.md links
their independent upstream PRs. Check versions before assuming those APIs exist.
This is a custom TSX renderer with signals, not React/DOM. Keep one ManagedWindow
and its ClientWindow, preserve CSD/SSD/fullscreen branches, state persistence,
enable/disable cleanup, usable-area handling and IPC. Use the pinned fork's local
docs (docs/docs/configuration/) and packages/shoji_wm/src/ types when available.
What ships with it
1 file beside SKILL.md 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.
- 11d ago Changed 744af96c2c4a
- 17d ago First seen · 75 lines · 50 tokens per session scan A b51488cfe4c5
shojiwm is a skill published in the GitHub repository howdeploy/kisa-stack (55 stars, last pushed 11d ago), licensed MIT. It adds 50 tokens to every session and 949 once invoked, about $0.0002 per session on Opus 5.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-09-29.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…