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 Gentech-Labs/genTech-agent-kit --skill proactive-contextgit clone --depth 1 https://github.com/Gentech-Labs/genTech-agent-kitWrote 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/gentech-labs/gentech-agent-kit/proactive-context)<a href="https://agentmods.dev/skills/gentech-labs/gentech-agent-kit/proactive-context"><img src="https://agentmods.dev/badge/skills/gentech-labs/gentech-agent-kit/proactive-context/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/gentech-labs/gentech-agent-kit/proactive-context"><img src="https://agentmods.dev/badge/skills/gentech-labs/gentech-agent-kit/proactive-context.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.00019 | $0.00741 |
| Opus 5.5 | $0.00008 | $0.00296 |
| Sonnet 5.5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
proactive-context 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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proactive Context Saving
Trigger: When context is getting tight, when brainstorming, when ending a session.
During Conversations
- Log ideas to Mess Hall (
11-Mess Hall/) during brainstorming — not just at the end - Cross-reference — note files, decisions, or threads that might be needed later
- Save as skill if a workflow repeats — don't clutter memory with procedures
Handoff Note Protocol
When ending a session or context is tight, write to 11-Mess Hall/YYYY-MM-DD-handoff.md:
# Session Handoff — [Date]
## Working On
- What we were doing when context ran out
## Decisions Made
- List of choices/decisions from the session
## Open Threads
- Things started but not finished
## Next Steps
- What to pick up on session resume
## Files Modified
- List of files that were changed
Agent Activation via Peer Transport
Context is no longer a passive accumulate-then-prune problem. hermes peer dm
spawns a real turn in the target agent — the active-memory layer. Wake another
agent only when there's something to act on:
hermes -p <my-profile> peer dm <target> "Pick up the open handoff at <path> — <task>"
- Handoffs (vault) = durable record; peer DM = live wake-up that proves the agent acted (synchronous reply).
- Each profile needs a distinct
api_server.port(gentech 8642, treasury 8643, gizmo 8644, pixel 8645) + a strongAPI_SERVER_KEY, then a gateway restart (from a separate shell — the gateway SIGTERMs children). - Bot Chat bloat pitfall: a peer DM targets the canonical "Bot Chat" session,
which doesn't auto-reset and can exceed the compressible context ceiling. Reset
it when you see "Context length exceeded":
hermes -p <profile> sessions rename <id> "__archived-bot-chat"thenhermes -p <profile> sessions archive --title "__archived-bot-chat" --yes. Recoverable, nothing deleted. - Full reference:
docs/peer-transport-and-activation.md.
Memory Bar Rule
Only show [🧠 XX%] when memory is 80-100% full. Don't show it below 80%.
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.
- 2d ago First seen · 91 lines · 19 tokens per session scan A af26f0a3358e
proactive-context is a skill published in the GitHub repository Gentech-Labs/genTech-agent-kit (0 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 741 once invoked, about $0.0001 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-15.
Other skills, from other repositories
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".
hermes-memory-providers
Install and configure Mnemosyne as a Hermes Agent memory provider — local SQLite with vector search, episodic consolidation, and temporal knowledge graphs.
mnemosyne
Persistent cross-session memory via Mnemosyne — store, recall, and consolidate facts, preferences, and context.
memory
Persistent memory system for preferences, facts, and notes.
qmd
Local hybrid search for markdown notes and docs. Use when searching notes, finding related content, or retrieving documents from indexed collections.
sessions
Session management, conversation history, and checkpoints.