A command for searching or filtering Orion's reports about unusual signals, such as changes from an expected baseline.

It helps find the latest signals, filter by info, notable, or critical severity, and search topics such as eclipses or block time.

It quickly narrows reports by severity or topic and shows the evidence recorded for each match.

How orioninfra/orion-agent-kit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to orioninfra/orion-agent-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/orioninfra/orion-agent-kit/main/.claude/commands/signals.md

Clone the repo

git clone --depth 1 https://github.com/orioninfra/orion-agent-kit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/orioninfra/orion-agent-kit/signals/github.svg)](https://agentmods.dev/commands/orioninfra/orion-agent-kit/signals)

Your own site

<a href="https://agentmods.dev/commands/orioninfra/orion-agent-kit/signals"><img src="https://agentmods.dev/badge/commands/orioninfra/orion-agent-kit/signals/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/orioninfra/orion-agent-kit/signals"><img src="https://agentmods.dev/badge/commands/orioninfra/orion-agent-kit/signals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 137 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00137
Opus 5.5	$0.00004	$0.00055
Sonnet 5.5	$0.00002	$0.00027
Haiku 4.5	$0.00001	$0.00014

Measured 2mo ago against content hash 4fa734c9e859, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

signals 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 2mo 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.

.claude/commands/signals.md · 12 lines

What it actually says

The user wants signals: $ARGUMENTS

If the argument looks like a severity (info / notable / critical), call get_signals with that min_severity.
If it looks like a keyword or topic (e.g. "eclipse", "block time"), call search_reports with it as query.
If empty, call get_signals for the latest report.

Report each match with date, severity, observed value vs baseline, and source. If nothing matches, say so plainly — do not speculate.

Changes

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.

2mo ago First seen · 12 lines · 10 tokens per session scan A 4fa734c9e859

Subscribe to this mod's changes

signals is a command published in the GitHub repository orioninfra/orion-agent-kit (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 137 once invoked, about $0.0000 per session on Opus 5.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.

Analytics and metrics ai-agents celestia data-availability mcp modular

signals next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
signalsorioninfra/orion-agent-kit	Command	1	3mo ago	Apache-2.0	A	10	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

orion-agent-kit: Command for Claude Code