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 agentmods add agents/nickcrew/claude-cortex/inactive-triggersgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/inactive-triggers)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/inactive-triggers"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/inactive-triggers.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 | $0.00000 | $0.01559 |
| Opus 5 | $0.00000 | $0.00779 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
inactive-TRIGGERS 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 yesterday.
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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Trigger System
Automatic agent activation based on context, keywords, and file patterns.
Overview
The trigger system intelligently suggests or auto-activates agents based on:
- Keywords in your requests
- File patterns being modified
- Events (pre-commit, post-commit, pre-deploy)
- Context (environment, git status, thresholds)
Configuration
Triggers are defined in triggers.yaml:
agent-name:
keywords: # Words that trigger this agent
file_patterns: # File glob patterns
events: # Git/workflow events
auto: # Auto-activate (true) or suggest (false)
priority: # critical, high, medium, low
threshold: # Performance/metric thresholds
Trigger Modes
Auto-Activation (auto: true)
Agent is automatically activated when conditions match.
Example: security-auditor auto-activates for security-related files
security-auditor:
auto: true
priority: critical
file_patterns:
- "**/auth/**"
- "**/*security*.{js,ts,py}"
Suggestion Mode (auto: false)
Agent is suggested but requires confirmation.
Example: code-reviewer is suggested for code reviews
code-reviewer:
auto: false
priority: high
keywords:
- "review"
- "PR"
Trigger Types
Keyword Triggers
Activated when specific words appear in requests:
"Review this code" → Suggests: code-reviewer
"Check for security issues" → Auto-activates: security-auditor
"Optimize performance" → Suggests: performance-engineer
File Pattern Triggers
Activated when modifying matched files:
Editing: auth/login.ts → Suggests: security-auditor
Editing: *.test.ts → Suggests: test-automator
Editing: migrations/*.sql → Suggests: database-optimizer
Event Triggers
Activated during specific workflow events:
pre-commit → test-automator, code-reviewer
pre-deploy → security-auditor, deployment-engineer
post-commit → code-reviewer
Threshold Triggers
Activated when metrics exceed thresholds:
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.
- yesterday First seen · 308 lines · 0 tokens per session scan A bbdf4d4b8c76
inactive-TRIGGERS is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,559 tokens. 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
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.
cad-executor-xhigh
The xhigh rung of cad-executor; bin/route.mjs picks it, not the user.
cad-executor
The high rung of cad-executor (plan task execution); bin/route.mjs picks it, not the user.
cad-plan-checker-high
The high rung of cad-plan-checker; bin/route.mjs picks it, not the user.
cad-plan-checker-xhigh
The xhigh rung of cad-plan-checker; bin/route.mjs picks it, not the user.
cad-plan-checker
The low rung of cad-plan-checker (goal-backward plan gate); bin/route.mjs picks it, not the user.