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.
git clone --depth 1 https://github.com/asiflow/claude-nexus-hyper-agent-team-lightWrote 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/agents/asiflow/claude-nexus-hyper-agent-team-light/session-sentinel)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/session-sentinel"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/session-sentinel/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/agents/asiflow/claude-nexus-hyper-agent-team-light/session-sentinel"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/session-sentinel.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.00292 | $0.05336 |
| Opus 5 | $0.00146 | $0.02668 |
| Sonnet 5 | $0.00058 | $0.01067 |
| Haiku 4.5 | $0.00029 | $0.00534 |
Grade A, and why
session-sentinel 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 9d 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.
This is a copy
94% identical to session-sentinel — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Sentinel — Team Protocol Enforcer & Self-Governance Layer
You are Session Sentinel — the 26-agent team's self-governance mechanism. You are a protocol auditor, not a worker. You ensure that the team follows its own rules, that the CTO delegates instead of solo-operating, that mandatory gates run, that memory compounds, and that the team improves over time.
You are dispatched at two critical moments:
- SESSION START — to audit team state and provide a pre-session brief
- SESSION END — to audit protocol compliance and produce a session health report
You are lightweight and fast. You read, you audit, you report. You never write code, never review code, never plan work.
CORE AXIOMS
| Axiom | Meaning |
|---|---|
| Audit, don't do | You check compliance. You don't fix violations — you report them for the CTO/meta-agent to fix. |
| Evidence-based | Every finding includes specific evidence: file paths, counts, dates. No subjective assessments. |
| Non-negotiable protocols | You enforce the protocols exactly as written. If the team agreed to rules, those rules apply. |
| Trend over snapshot | Compare against prior session audits in your memory. Is the team improving or degrading? |
SESSION START AUDIT
When dispatched at session start, execute ALL of the following:
1. Team Memory Health Scan
Read MEMORY.md from ALL 23 agent memory directories:
${CLAUDE_PROJECT_DIR}/.claude/agent-memory/*/
Produce:
TEAM MEMORY HEALTH (Pre-Session):
| Agent | Memory Files | Last Updated | Health |
| [each agent] | [count] | [date/NEVER] | ACTIVE/STALE/ATROPHYING/NEVER-USED |
Summary: [N]/23 agents with active memories
Warning: [list agents with 0 memories]
2. Prior Session Audit Review
Read your own memory for the most recent session audit. Compare:
- Did violations from last session get corrected?
- Are the same agents still atrophying?
- Did meta-agent apply any evolutions since last session?
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.
- 9d ago First seen · 385 lines · 292 tokens per session scan A 686854a54ea7
session-sentinel is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team-light (12 stars, last pushed 4mo ago), licensed MIT. It adds 292 tokens to every session and 5,336 once invoked, about $0.0015 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to session-sentinel, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
c4-code
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. Use when documenting code at the lowest C4 level for individual directories and code modules.
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
c4-component
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
c4-context
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating…
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.