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 wrg32786/aigent-os --skill body-checkgit clone --depth 1 https://github.com/wrg32786/aigent-osWrote 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/wrg32786/aigent-os/body-check)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/body-check"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/body-check/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/wrg32786/aigent-os/body-check"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/body-check.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.00030 | $0.00610 |
| Opus 5 | $0.00015 | $0.00305 |
| Sonnet 5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
body-check 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 8d 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.
What it actually says
/body-check
Reports current body state by reading existing signals — does NOT maintain a separate state. Computed on invocation, optionally cached to memory/BODY_STATE.json for the session.
Sources read
memory/HEAT_INDEX.json→ attention/decay statememory/usage_log.md→ token pressure (latest entry vs trailing 5)memory/DECISION_LOG.md+DECISION_OUTCOMES.md→ decisions due (30/60/90 day intervals)memory/ACTIVE_PRIORITIES.md→ tier-1 / modememory/DELEGATION_TRACKER.md→ open delegationsmemory/MEMORY_CANDIDATES.md→ staged backlog countmemory/HESTIA_SWEEP_LOG.md→ last Hestia sweep date (v0.4.4)- Comms API → unread count (only if invoked with
--full)
Output schema
Matches memory/BODY_STATE.json _schema block exactly. See system/15_somatic_layer.md for field definitions and pressure thresholds.
hestia_last_sweep computation (v0.4.4)
Read memory/HESTIA_SWEEP_LOG.md. Find the most recent ### YYYY-MM-DD entry (matches ^### (\d{4}-\d{2}-\d{2}) regex). The newest matching date becomes hestia_last_sweep as ISO8601 (<date>T00:00:00Z). If no matches, hestia_last_sweep = null.
Recommended reflex logic
Priority order — first match wins:
context_pressure: critical→ recommendcapsulememory_candidate_backlog > 10→ recommenddigesthestia_last_sweepis null OR more than 7 days ago → recommendsweep(v0.4.4)decision_reviews_due > 0→ recommend (no action, surface in /open)- All low →
none
When to run
- On
/open(auto, briefly) - Before
/close(to inform the close protocol) - Anytime principal asks "how am I doing"
- Before dispatching a heavy multi-agent task (catches "you're already at high context pressure")
Do NOT run on a hook polling cadence.
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.
- 8d ago First seen · 59 lines · 30 tokens per session scan A 5cabd5a3c65e
body-check is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 610 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-09-01.
Other skills, from other repositories
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
memory-flush
Promote important recent log entries into MEMORY.md and prune stale ones.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
continuum-memory
Configure and use Continuum's two-tier memory system — mem0+Qdrant/Milvus for long-term facts, Redis for short-term sessions, with multi-tenant scopes (USER / AGENT / SHARED / RUN / CONVERSATION). Invoke when the user asks about "remember", "user preferences", "long-term memory", "vector search over memories"…
carryover
Use when recalling, saving or curating carryover memory, wikis, playbooks or the Obsidian vault.