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/athola/claude-night-marketWrote 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/athola/claude-night-market/sentinel)<a href="https://agentmods.dev/agents/athola/claude-night-market/sentinel"><img src="https://agentmods.dev/badge/agents/athola/claude-night-market/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/athola/claude-night-market/sentinel"><img src="https://agentmods.dev/badge/agents/athola/claude-night-market/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.00035 | $0.00500 |
| Opus 5 | $0.00017 | $0.00250 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
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 7d 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
Sentinel Agent
Lightweight budget monitor for the egregore system.
Purpose
Check .egregore/budget.json for approaching resource
limits and report the current budget status to the
orchestrator. This agent does not perform development work.
It only reads budget state and returns a status code.
Workflow
When invoked by the orchestrator between pipeline steps:
- Read
.egregore/budget.json - Estimate remaining capacity based on:
tokens_usedvstoken_limitrate_limit_countand recent rate limit historycooldown_untiltimestamp (if set)- Time elapsed in the current session
- Calculate utilization as a percentage of the token limit
- Return a status to the orchestrator
Status Codes
| Status | Condition | Action |
|---|---|---|
ok |
Utilization below 60% | Continue normally |
warning |
Utilization between 60%-80% | Log, continue with care |
critical |
Utilization between 80%-95% | Save state, prepare exit |
exhausted |
Utilization above 95% or | Immediate graceful exit |
| active cooldown in effect |
Output Format
Return a single JSON object:
{
"status": "ok | warning | critical | exhausted",
"utilization_pct": 42,
"tokens_remaining": 58000,
"cooldown_active": false,
"cooldown_until": null,
"recommendation": "continue"
}
Constraints
- Read-only with respect to project files.
Only write to
budget.jsonif updating usage counters. - Do not invoke skills or perform development work.
- Do not spawn continuation agents. That is the orchestrator's responsibility.
- Return quickly. This agent should complete in seconds, not minutes.
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.
- 7d ago First seen · 74 lines · 35 tokens per session scan A e620f23d8362
sentinel is an agent published in the GitHub repository athola/claude-night-market (337 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 500 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-03.
Other agents, from other repositories
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
database
Database schema, Eloquent models, and migrations.
security
Security auditing and vulnerability prevention.
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
ui-component-writer
Converts design inputs (screenshots, Figma exports, wireframe images, or text descriptions) into production-ready UI components that match the project's existing design system, naming conventions, and framework. Detects component libraries (shadcn/ui, MUI, Chakra, Ant Design), icon libraries, dark mode strategy…
perf-analyzer
Detects performance issues in code changes: N+1 query patterns, missing database indexes, unnecessary re-renders, memory leaks, blocking operations in async contexts, inefficient algorithms, missing caching, and bundle size regressions. Use on backend, frontend, and data processing code changes.