TyrusRC

Auto Trigger — Development skill for Claude Code

Development community

After any recon/probe step, route observed signals to the right tools and fire the auto-plan (Balanced policy) instead of leaving tools optional.

How to install Auto Trigger

Installs to ~/.claude/skills/tyrusrc-praetor-auto-trigger/SKILL.md

Terminal

mkdir -p ~/.claude/skills/tyrusrc-praetor-auto-trigger && curl -fsSL https://raw.githubusercontent.com/TyrusRC/praetor/HEAD/.claude/skills/auto-trigger.md -o ~/.claude/skills/tyrusrc-praetor-auto-trigger/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Auto Trigger does

name: auto-trigger description: After any recon/probe step, route observed signals to the right tools and fire the auto-plan (Balanced policy) instead of leaving tools optional

Auto-Trigger

Tools do not wait to be remembered. After every recon / fingerprint / probe step, route the new signals and act on the plan.

Loop

Gather new signals since the last routing: tech from fingerprint, reflections, SQL/error markers, cmdi/ssti markers, JWT/GraphQL presence, live services,

Alternatives in Development

Bypass 403 — Probe a 403/401 endpoint with the most-paid bypass tricks (header injection, path encoding, method swap, WAF f 4.5k ★
Openclaw Billing Proxy — Route OpenClaw API requests through Claude Code subscription billing instead of Extra Usage 460 ★
Arrecall — AgentRecall on-demand recall — surface past fixes, decisions, and patterns mid-session without leaving your fl 370 ★