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 SoliEstre/EstreGenesis --skill hyperbrief-trigger-checkgit clone --depth 1 https://github.com/SoliEstre/EstreGenesisWrote 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/soliestre/estregenesis/hyperbrief-trigger-check)<a href="https://agentmods.dev/skills/soliestre/estregenesis/hyperbrief-trigger-check"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/hyperbrief-trigger-check.svg" alt="Measured on agentmods" 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.00406 | $0.04266 |
| Opus 5 | $0.00203 | $0.02133 |
| Sonnet 5 | $0.00081 | $0.00853 |
| Haiku 4.5 | $0.00041 | $0.00427 |
Grade A, and why
hyperbrief-trigger-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 today.
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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hyperbrief Trigger Check — the escalation gate
You are about to ask the user a decision question, OR Superscalar just opened a write/deploy/send lane, OR an inbound DECISION_REQUEST arrived. Before composing the message, run this 30-second rubric.
1. Trigger detection
Run this skill if ANY of these apply:
- Next assistant message will contain
괜찮을까요/할까요/should we/which (one|option)/approve/confirm/choose between/OK to/ similar decision-soliciting patterns. - Superscalar fan-out just opened a
write/deploy/sendlane (Superscalar's irreversibility barrier touches a default-forbidden action). - Inbound A2A is
CUSTOM/DECISION_REQUESTrequiring response. - About to call
AskUserQuestiontool.
Skip if:
- All fan-out lanes are read-only (no side effects).
- This is a continuation of an already-decided plan within the same approved Phase (Constellation §4: "no confirming planned dispatch").
1.5 Audience-profile command routing (v0.6+)
Independent of the escalation rubric, certain user inputs are audience-profile commands that must be forwarded to the hyperbrief skill (which owns AudienceProfileFallback IR population) for parsing + persistence, regardless of whether a decision is being made.
Recognized command shapes (parse BEFORE the escalation rubric; if matched, route AND continue):
- Tone profile:
L<a>.<b>.<c>(e.g.L1.1.1,L2.2.2) — setsaudience_profile_fallback.tone_profile. - term_pairing command (v0.6, additive):
L<a>.<mode>.<scope>[suffix]where:mode∈{E, I, N}(every / initial / none).scope∈{C, D, B, R}(conversation / document / board / review) — multi-scope via+(e.g.C+B), or shortcutA(=C+D+B+R).- optional
suffix:!(force retroactive_apply = Y),?(force retroactive_apply = prompt). - Examples:
L1.I.C/L1.E.A/L2.N.D/L1.I.C+B/L2.E.D!/L1.I.A?.
- Combined (single token, dot-chained): tone command followed by term_pairing command in the same utterance — both apply.
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.
- today Changed 3ad6c60dfdf1
- 6d ago First seen · 212 lines · 406 tokens per session scan A fc19c2e84441
hyperbrief-trigger-check is a skill published in the GitHub repository SoliEstre/EstreGenesis (8 stars, last pushed today), licensed Apache-2.0. It adds 406 tokens to every session and 4,266 once invoked, about $0.0020 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
update-agent-context
This skill should be used to keep CLAUDE.md, AGENTS.md, and the skill files themselves compact, current, and internally consistent. It runs in three phases: Phase 1 performs a one-time structural refactor of CLAUDE.md using a Karpathy-inspired behavioral scaffold and derives AGENTS.md from it by stripping Claude…
watercooler-onboarding
Bootstrap Watercooler memory for a repository by inspecting local code, docs, CI, git history, and existing Watercooler threads, then writing a small set of durable, provenance-backed seed threads that future agents can query and extend. Use when entering a repo for the first time, seeding a repo with Watercooler…
ppgp
Portable Persistent Goal Protocol for long-running coding-agent work. Use when starting, resuming, handing off, distilling, or closing a substantial software goal across long sessions, context compaction, agent replacement, or other Agent Skills-compatible coding-agent environments.
search-threads
Search threads with filters. Supports filters like role:planner, type:Decision, after:2024-01, thread:topic-name, status:OPEN.
watercooler-health
Check watercooler system health — MCP server, baseline graph (T1), git auth, GitHub rate limit, and daemons. Use when syncs break or anything in the watercooler stack behaves unexpectedly.
recall
Recall project context or answer questions about history and decisions. Use before starting work, when investigating unfamiliar code, or asking "What was decided about X?" / "Why did we choose Y?".