Skip to content
Back to skills

Hedge Router Status

ASecurity

Show or explain local compute spend, token exposure, and hedge paper P&L. Use when the user asks about hedge router status, compute exposure, gateway spend, or paper hedge results.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 22, 2026
ai-agents

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add kapilcdave/hedge-router --skill hedge-router-status --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hedge Router Status?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Hedge Router Status
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kapilcdave-hedge-router-status/badge)](https://www.skillsdirectory.com/skills/kapilcdave-hedge-router-status)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: hedge-router-status
description: Show or explain local compute spend, token exposure, and hedge paper P&L. Use when the user asks about hedge router status, compute exposure, gateway spend, or paper hedge results.
---

# hedge router status

Run `hedge-router status` to obtain the current compact, read-only status. Report the output exactly when the user only asks for status. Run `hedge-router report` when the user asks for a detailed explanation, then summarize compute spend, token exposure, gateway sources, and paper results in plain language.

Never claim that paper P&L is live trading profit. It is simulated research output. Do not read or expose prompts, code, filenames, paths, tool arguments, or tool output while reporting status.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…