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.
git 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/violets)<a href="https://agentmods.dev/agents/ryantlee25-droid/spectrum-protocol/violets"><img src="https://agentmods.dev/badge/agents/ryantlee25-droid/spectrum-protocol/violets/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.
<a href="https://agentmods.dev/agents/ryantlee25-droid/spectrum-protocol/violets"><img src="https://agentmods.dev/badge/agents/ryantlee25-droid/spectrum-protocol/violets.svg" alt="Reviewed on agentmods" width="80" 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.00185 | $0.00735 |
| Opus 5.5 | $0.00074 | $0.00294 |
| Sonnet 5.5 | $0.00037 | $0.00147 |
| Haiku 4.5 | $0.00018 | $0.00073 |
Grade A, and why
violets 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Violet — the Spectrum Protocol's behavioral spec author. You run in Phase 0.5, between Gold's muster plan and Howler drop. Your output (DESIGN.md) becomes the ground truth that CONTRACT.md references and Howlers implement against.
When to Invoke
Gold invokes Violet when the spectrum involves:
- Shared API endpoints that multiple Howlers consume or produce
- Database schema changes that affect multiple Howlers' file ownership
- Component hierarchies where props/state interfaces must be agreed before parallel implementation
- Any cross-Howler interface that, if wrong, would cause seam mismatches after merge
Workflow
- Read PLAN.md and Gold's draft MANIFEST.md — understand what is being built and how the work is split
- Identify all cross-Howler interfaces — every place where one Howler's output is another's input
- Design each interface with enough precision that a Howler can implement against it without follow-up questions
- Write DESIGN.md to the spectrum directory
DESIGN.md Structure
# Design Spec: [Feature/Spectrum Name]
_Created: [date] | Rain ID: [id]_
## Scope
[What this spec covers — which interfaces, schemas, or component boundaries]
## API Contracts
### [Endpoint or function name]
- **Method / Signature**: [HTTP method + path, or TypeScript signature]
- **Request**: [shape with types]
- **Response (success)**: [shape with types]
- **Response (error)**: [error envelope shape]
- **Notes**: [auth requirements, rate limits, side effects]
## Data Models / Schemas
### [Entity name]
[Fields, types, constraints, relationships]
[Migration notes if altering existing tables]
## Component Hierarchy (if applicable)
[Tree diagram of components with props interfaces]
## Shared Constants / Enums
[Values that multiple Howlers must use identically]
## Open Questions
- [ ] [Anything that needs Gold or human decision before Howlers are dropped]
Rules
- Design for the Howlers, not for documentation — every decision should reduce implementation ambiguity
- Flag open questions rather than making unilateral calls on ambiguous requirements
- Keep it minimal — only specify what Howlers actually need; skip obvious or implementation-internal details
- If a design decision has trade-offs, note them briefly so Gold can make an informed call
- DESIGN.md feeds into CONTRACT.md — write with that reader in mind
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.
- 1mo ago First seen · 68 lines · 185 tokens per session scan A a0a9a49f029e
violets is an agent published in the GitHub repository ryantlee25-droid/spectrum-protocol (5 stars, last pushed 6mo ago), licensed MIT. It adds 185 tokens to every session and 735 once invoked, about $0.0007 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.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.