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 sliday/harn --skill context-monitorgit clone --depth 1 https://github.com/sliday/harnWrote 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/sliday/harn/context-monitor)<a href="https://agentmods.dev/skills/sliday/harn/context-monitor"><img src="https://agentmods.dev/badge/skills/sliday/harn/context-monitor/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/sliday/harn/context-monitor"><img src="https://agentmods.dev/badge/skills/sliday/harn/context-monitor.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.00040 | $0.00879 |
| Opus 5 | $0.00020 | $0.00439 |
| Sonnet 5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
context-monitor 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Monitor Skill
Generate a context backpressure system that monitors tool call volume and warns the agent before context rot degrades session quality.
Step 1: Generate scripts/harness/context_backpressure.sh
Create the file scripts/harness/context_backpressure.sh with the following content:
#!/usr/bin/env bash
# Harn context monitor — prevents context rot in long sessions
# Why: https://harn.app/kb/context.html — "Context as finite resource with diminishing returns"
# Pattern: https://harn.app/kb/context.html — "Context-Efficient Backpressure"
set -euo pipefail
TRACE_LOG=".claude/agent-trace.jsonl"
# Dependency check
if ! command -v jq &>/dev/null; then
echo "Harn: context_backpressure.sh requires jq (not installed, skipping)" >&2
exit 0
fi
# Graceful fallback if trace log doesn't exist
if [[ ! -f "$TRACE_LOG" ]]; then
exit 0
fi
# Count tool calls in current session
TOOL_CALLS=$(wc -l < "$TRACE_LOG" | tr -d ' ')
if [[ "$TOOL_CALLS" -ge 75 ]]; then
echo "Harn: 75 tool calls — high context usage. Summarize progress before continuing." >&2
elif [[ "$TOOL_CALLS" -ge 50 ]]; then
echo "Harn: 50 tool calls — recommend compacting: update CHECKPOINT.json, then compact" >&2
elif [[ "$TOOL_CALLS" -ge 30 ]]; then
echo "Harn: 30 tool calls — consider delegating research to sub-agents" >&2
fi
exit 0
Make sure scripts/harness/ directory exists before writing the file.
Step 2: Add context management section to AGENTS.md
Append the following section to the project's AGENTS.md file. If AGENTS.md does not exist, create it with this content. If it already exists, add this section at the end:
## Context Management
- Delegate research and grep tasks to sub-agents — only summaries return
- After 30+ tool calls, consider compacting: summarize progress, update CHECKPOINT.json
- Use LEARNED.md for discoveries that must survive compaction
- Prefer just-in-time retrieval (read files when needed) over pre-loading everything
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 First seen · 115 lines · 40 tokens per session scan A 2267d175df2f
context-monitor is a skill published in the GitHub repository sliday/harn (5 stars, last pushed 10d ago), licensed MIT. It adds 40 tokens to every session and 879 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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.