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/kcdjmaxx/homaruscc/alignnpx skills add kcdjmaxx/HomarUScc --skill aligngit clone --depth 1 https://github.com/kcdjmaxx/HomarUSccWhat 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.04710 |
| Opus 5 | $0.00019 | $0.02355 |
| Sonnet 5 | $0.00008 | $0.00942 |
| Haiku 4.5 | $0.00004 | $0.00471 |
Grade A, and why
align 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.
How it starts
The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/align — Identity Alignment Interview
Conducts a structured 10-domain interview that maps your values, preferences, and boundaries into HomarUS identity files. This is how a new agent learns who its operator is.
Based on the Alignment Generator and alignment-interview-cc.
When to Trigger
- User invokes
/align - First-boot detection: if the identity directory's
soul.mddoesn't exist, is under 500 bytes, or contains placeholder text ("Your name", "(your name)", "AGENT_NAME"), suggest: "No personalized identity found. Want to run /align to set me up?" - User says "set up identity", "configure personality", "onboarding", or similar
How It Works
1. Setup
Determine the identity directory:
- Check if both
~/.homarus/and~/.homaruscc/exist. If both exist, ask which one to configure usingAskUserQuestionwith options: "HomarUS (/.homarus/)" and "HomarUScc (/.homaruscc/)". - If only
~/.homarus/exists, use~/.homarus/identity/ - If only
~/.homaruscc/exists, use~/.homaruscc/identity/ - If neither exists, create
~/.homarus/identity/(the open-source default)
Create the identity directory if it doesn't exist:
mkdir -p <identity_dir>
Overwrite protection: Check if soul.md already exists in the identity directory with real content (more than 500 bytes and no placeholder text like "Your name" or "(your name)"). If it does, warn the user:
"You already have identity files here. Running /align will overwrite soul.md and user.md. state.md, preferences.md, and disagreements.md will only be written if they don't exist. Continue, back up first, or cancel?"
Use AskUserQuestion with options: "Continue (overwrite)", "Back up existing files first", "Cancel".
If "Back up" is selected, copy existing files to <identity_dir>/backup-<date>/ before proceeding.
Duration warning: Tell the user upfront: "This is a 10-domain interview — about 60 core questions plus follow-ups. Budget ~30-45 minutes. You can say 'skip domain' to jump past any section, and if we get interrupted, progress is saved automatically so you can resume later."
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.
- yesterday First seen · 364 lines · 38 tokens per session scan A a9b1cd78094c
align is a skill published in the GitHub repository kcdjmaxx/HomarUScc (1 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 4,710 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.