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 blackmo18/realm --skill realm-statusgit clone --depth 1 https://github.com/blackmo18/realmWrote 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/blackmo18/realm/realm-status)<a href="https://agentmods.dev/skills/blackmo18/realm/realm-status"><img src="https://agentmods.dev/badge/skills/blackmo18/realm/realm-status/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/blackmo18/realm/realm-status"><img src="https://agentmods.dev/badge/skills/blackmo18/realm/realm-status.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.00049 | $0.00708 |
| Opus 5.5 | $0.00020 | $0.00283 |
| Sonnet 5.5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
realm-status 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
realm-status
Host invocation: Claude Code and Gemini use /realm-status; Codex uses $realm-status.
Inspect Realm state without writing.
When to Use
| Trigger | Example |
|---|---|
| Check vault vs staged | "realm status", /realm-status |
| Verify init completed | After /realm-forge |
| Verify vault health | "what does realm know" |
| Orient at session start | "what does realm know?" |
When NOT to Use
- Want to investigate code + vault →
/realm-fathom - Want to plan architectural changes →
/realm-planning realm-state.jsonmissing → will report; run/realm-forge
Procedure
Handle all steps inline using Read and Bash. No agent spawn.
Step 1 — Read state
Read <projectRoot>/.realm/realm-state.json.
If missing:
No realm state found.
Run /realm-forge to bootstrap.
STOP.
Extract: vaultPath, projectSlug, projectDir.
Step 1.5 — Check orchestration lock
python3 "<realmOrchestrateSkillDir>/scripts/orchestrate.py" state --project-root .
(Resolve realmOrchestrateSkillDir the same way realm-orchestrate/SKILL.md does —
sibling skill directory, not a relative path.) If ORCH_ACTIVE=true, remember
RUN_ID and WAVE for the print in Step 3. If the orchestrate skill isn't
installed or the call errors, skip this step silently — orchestration status is
supplementary, not required for /realm-status to work.
Step 2 — Count nodes by type
Read the live vault tree with one bounded command:
find <projectDir> -name "*.md" -not -path "*/_templates/*" | sort
Group results by leading path segment (decisions/foo.md → decisions/). Strip .md
suffix for [[id]] display. Use file mtime for date display.
Tag frequency (run once):
grep -rh "^ - " <projectDir> --include="*.md" 2>/dev/null | sort | uniq -c | sort -rn | head 20
Step 3 — Print status (caveman-compressed)
realm:<projectSlug>
vault:<vaultPath> proj:<projectDir>
⚡ ORCHESTRATION ACTIVE <RUN_ID> — wave <WAVE> (only when ORCH_ACTIVE=true from Step 1.5)
NODES <total>
decisions/<N>: [[id]] <date> [[id2]] <date>
discoveries/<N>: [[id]] <date>
sessions/<N>: <filename>
TAGS #<tag>:<N> #<tag>:<N> #<tag>:<N> (top 10)
→ vault current. Run /realm-fathom to investigate code or /realm-planning to design.
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.
- 1mo ago First seen · 90 lines · 49 tokens per session scan A cdc9ec495828
realm-status is a skill published in the GitHub repository blackmo18/realm (0 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 708 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-10-02.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
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
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
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…