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.
curl -O https://raw.githubusercontent.com/orioninfra/orion-agent-kit/main/.claude/commands/signals.mdgit clone --depth 1 https://github.com/orioninfra/orion-agent-kitWrote 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/commands/orioninfra/orion-agent-kit/signals)<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="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.1 | $0.00010 | $0.00137 |
| Opus 5 | $0.00005 | $0.00068 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
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 8d 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
The user wants signals: $ARGUMENTS
- If the argument looks like a severity (info / notable / critical), call
get_signalswith thatmin_severity. - If it looks like a keyword or topic (e.g. "eclipse", "block time"), call
search_reportswith it asquery. - If empty, call
get_signalsfor the latest report.
Report each match with date, severity, observed value vs baseline, and source. If nothing matches, say so plainly — do not speculate.
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.
- 8d ago First seen · 12 lines · 10 tokens per session scan A 4fa734c9e859
signals is a command published in the GitHub repository orioninfra/orion-agent-kit (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 137 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.