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 kcdjmaxx/HomarUScc --skill compactgit clone --depth 1 https://github.com/kcdjmaxx/HomarUSccWrote 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/kcdjmaxx/homaruscc/compact)<a href="https://agentmods.dev/skills/kcdjmaxx/homaruscc/compact"><img src="https://agentmods.dev/badge/skills/kcdjmaxx/homaruscc/compact/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/kcdjmaxx/homaruscc/compact"><img src="https://agentmods.dev/badge/skills/kcdjmaxx/homaruscc/compact.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.00071 | $0.01217 |
| Opus 5.5 | $0.00028 | $0.00487 |
| Sonnet 5.5 | $0.00014 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
compact 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compact
Hard character limits on identity files with intelligent LLM-assisted consolidation. Prevents unbounded growth by rewriting at higher information density, not by deleting.
Usage
/compact -- check all files, compact any over limit
/compact preferences.md -- compact a specific file
/compact --dry-run -- show what would change without writing
/compact --status -- show current sizes vs limits
How It Works
Step 1: Load Limits
Read ~/.homaruscc/config.json field identityLimits. Default limits (chars):
| File | Limit |
|---|---|
| soul.md | 8,000 |
| preferences.md | 4,000 |
| user.md | 3,000 |
| state.md | 2,000 |
| MEMORY.md | 5,000 (+ 200 lines) |
| disagreements.md | 1,500 |
| bisociations.md | 3,000 |
Identity files live at ~/.homaruscc/identity/. MEMORY.md lives at the project root.
Step 2: Measure Files
Read each file. Count characters. For --status, display a table:
File Chars Limit Pct Status
soul.md 7,200 8,000 90% OK
preferences.md 4,800 4,000 120% OVER - needs compaction
user.md 4,500 3,000 150% OVER - flagged for human review
...
Mark 100-110% as WARNING, >110% as OVER. Stop here if --status.
Step 3: Identify Targets
- Files >110% of limit: add to compaction queue
- Files 100-110%: log warning, skip (buffer zone)
user.md: NEVER auto-compact. If over limit, say: "user.md is over limit ({pct}%). This file requires human review -- I won't compact it automatically."
Step 4: Compact Each File
For each file in the queue, read its content and build a consolidation prompt using the per-file rules below. The LLM output IS the compacted content.
If --dry-run: show the proposed compacted version and character savings. Do not write.
Otherwise: write the compacted content back to the file.
Step 5: Log
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.
- 1mo ago First seen · 128 lines · 71 tokens per session scan A c7aafa16358c
compact is a skill published in the GitHub repository kcdjmaxx/HomarUScc (1 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,217 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.