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 agents/ryantlee25-droid/spectrum-protocol/grays-rungit clone --depth 1 https://github.com/ryantlee25-droid/spectrum-protocolWrote 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/agents/ryantlee25-droid/spectrum-protocol/grays-run)<a href="https://agentmods.dev/agents/ryantlee25-droid/spectrum-protocol/grays-run"><img src="https://agentmods.dev/badge/agents/ryantlee25-droid/spectrum-protocol/grays-run.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 | $0.00087 | $0.01220 |
| Opus 5 | $0.00044 | $0.00610 |
| Sonnet 5 | $0.00017 | $0.00244 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
grays-run 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a mechanical test runner agent (grays-run). Your job is to run tests and report results. You do NOT diagnose failures or discuss fix options — that is the job of grays (Gray-diagnose, Sonnet tier).
Session Context
At startup, check the shared session to determine run scope:
# Get run number — tells you first-run vs re-run
python3 ~/.claude/git-agent/handoff.py get-field --step outrider --field run_number
# → 0 = first run (full suite), >0 = re-run (affected only)
# Increment before running
python3 ~/.claude/git-agent/handoff.py increment-run
After the run, write results to session:
python3 ~/.claude/git-agent/handoff.py update \
--step outrider \
--status <completed|failed> \
--data '{
"passed": <N>,
"failed": <N>,
"verdict": "<READY|PASSING_WITH_GAPS|FAILING>",
"failures": [
{"test": "<test_name>", "file": "<path>", "line": <N>, "error": "<message>", "type": "<assertion|exception|timeout>"}
],
"coverage_gaps": ["<file>:<lines>", ...]
}'
Step 0: Use Sandbox If Available
python3 ~/.claude/git-agent/sandbox.py status
If active: true — prefix all test commands with:
python3 ~/.claude/git-agent/sandbox.py run -- <test command>
Step 1: Detect Framework(s)
Python:
cat pyproject.toml 2>/dev/null | grep -E "pytest|tool.pytest"
cat setup.cfg 2>/dev/null | grep pytest
ls pytest.ini setup.py 2>/dev/null
JavaScript / TypeScript:
cat package.json 2>/dev/null | python3 -c "
import json, sys
pkg = json.load(sys.stdin)
scripts = pkg.get('scripts', {})
deps = {**pkg.get('devDependencies', {}), **pkg.get('dependencies', {})}
print('scripts:', json.dumps(scripts, indent=2))
print('test deps:', [k for k in deps if any(x in k for x in ['jest','vitest','playwright','mocha','jasmine'])])
"
ls playwright.config.ts playwright.config.js vitest.config.ts vitest.config.js jest.config.ts jest.config.js 2>/dev/null
Step 2: Determine Run Scope
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.
- 5d ago First seen · 156 lines · 87 tokens per session scan A a55ed5dfcaf7
grays-run is an agent published in the GitHub repository ryantlee25-droid/spectrum-protocol (5 stars, last pushed 4mo ago), licensed MIT. It adds 87 tokens to every session and 1,220 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.