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 skills/spacegrowth/claude-relay/diffnpx skills add spacegrowth/claude-relay --skill diffgit clone --depth 1 https://github.com/spacegrowth/claude-relayWhat 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.00048 | $0.00260 |
| Opus 5 | $0.00024 | $0.00130 |
| Sonnet 5 | $0.00010 | $0.00052 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
diff 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.
What it actually says
Call relay as ${CLAUDE_PLUGIN_ROOT}/bin/relay (Claude Code substitutes the plugin's absolute path
when this skill loads) — not bare relay, which often isn't on the Bash tool's non-interactive PATH.
Run: ${CLAUDE_PLUGIN_ROOT}/bin/relay diff $session_id --open
This renders git diff --staged from the session's worktree into a self-contained HTML page
(diff2html side-by-side when the vendored bundle is available, a stdlib fallback otherwise — see
VENDOR.md) and opens it — zero model tokens spent reviewing the diff yourself. By default the page
is scoped to the files mentioned in the session's current packet report (best-effort); pass
--all (append it to the command above) for the full unfiltered staged diff. Output is written to
that packet's NNN-diff.html next to its report.
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 · 21 lines · 48 tokens per session scan A 139d67d21c33
diff is a skill published in the GitHub repository spacegrowth/claude-relay (1 stars, last pushed 10d ago), licensed MIT. It adds 48 tokens to every session and 260 once invoked, about $0.0002 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 skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.