sso-mcp-server: Agent for Claude Code

.github/agents/rainbow.standardize.agent.md

rainbow.standardize is an agent for Claude Code from DauQuangThanh/sso-mcp-server. It costs 18 tokens per session (3,408 once invoked), scanned A, original, MIT.

An agent that creates coding standards and conventions documentation for an entire software product. It covers names, files, APIs, databases, testing, Git, and general documentation.

In plain words
What is it for?
Use it to standardize UI and code naming, project structure, API and database conventions, testing, Git workflows, and documentation.
Why use it?
It turns scattered project practices into one documented set of rules that developers can follow consistently.

Agent for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is DauQuangThanh/sso-mcp-server's own configuration. It tells Claude Code how to work on sso-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sso-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DauQuangThanh/sso-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/DauQuangThanh/sso-mcp-server/main/.github/agents/rainbow.standardize.agent.md
Clone the repo
git clone --depth 1 https://github.com/DauQuangThanh/sso-mcp-server

Made for: Claude Code.

Wrote 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.

agentmods badge for rainbow.standardize

README.md
[![agentmods](https://agentmods.dev/badge/agents/dauquangthanh/sso-mcp-server/rainbow.standardize/github.svg)](https://agentmods.dev/agents/dauquangthanh/sso-mcp-server/rainbow.standardize)
Your own site
<a href="https://agentmods.dev/agents/dauquangthanh/sso-mcp-server/rainbow.standardize"><img src="https://agentmods.dev/badge/agents/dauquangthanh/sso-mcp-server/rainbow.standardize/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.

agentmods 80×15 button for rainbow.standardize

Your own site · 80×15
<a href="https://agentmods.dev/agents/dauquangthanh/sso-mcp-server/rainbow.standardize"><img src="https://agentmods.dev/badge/agents/dauquangthanh/sso-mcp-server/rainbow.standardize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.03408
Opus 5 $0.00009 $0.01704
Sonnet 5 $0.00004 $0.00682
Haiku 4.5 $0.00002 $0.00341

Measured 9d ago against content hash 21d1175b1f2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

rainbow.standardize 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 9d 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.

.github/agents/rainbow.standardize.agent.md · 409 lines

How it starts

The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

IMPORTANT: Automatically generate a 'docs:' prefixed git commit message (e.g., 'docs: add coding standards and conventions') and commit upon completion.

  1. Setup: Run .rainbow/scripts/bash/setup-standardize.sh --json from repo root and parse JSON for STANDARDS_DOC, DOCS_DIR, ARCH_DOC, CONSTITUTION. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

  2. Load context: Read memory/ground-rules.md, docs/architecture.md (if exists), and all feature specifications from specs/*/spec.md. Load STANDARDS_DOC template (already copied to docs/).

  3. Execute standardization workflow: Follow the structure in STANDARDS_DOC template to:

    • Define UI naming conventions (MANDATORY)
    • Establish code naming conventions
    • Document file and directory structure standards
    • Define API design standards
    • Establish database naming conventions
    • Document testing standards
    • Define Git workflow and commit message conventions
    • Establish documentation standards
  4. Stop and report: Command ends after standards document completion. Report STANDARDS_DOC path and generated artifacts.

Phases

Phase 0: Standards Analysis & Best Practices Research

  1. Analyze project context:

    • Read architecture.md to understand technology stack
    • Detect UI layer presence: Check if project has frontend/UI components
      • Look for: React, Vue, Angular, HTML, CSS, mobile frameworks (React Native, Flutter, SwiftUI)
      • Check for: UI mockups, design specifications, frontend directories
      • Determine: Frontend project, backend-only, or full-stack
    • Read ground-rules.md for existing constraints
    • Read feature specs to identify naming patterns
    • Identify programming languages and frameworks in use
  2. Research best practices for each technology:

    • UI naming conventions for the UI framework (React, Vue, Angular, etc.)
    • Code naming conventions for the backend language (Python, Java, TypeScript, etc.)
    • Database naming conventions for the database system
    • API design standards (REST, GraphQL, gRPC, etc.)
    • Testing conventions for the test frameworks

Read the full file on GitHub · 409 lines

Changes

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.

  1. 9d ago First seen · 409 lines · 18 tokens per session scan A 21d1175b1f2a

Subscribe to this mod's changes

rainbow.standardize is an agent published in the GitHub repository DauQuangThanh/sso-mcp-server (0 stars, last pushed 8mo ago), licensed MIT. It adds 18 tokens to every session and 3,408 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.