ring:qa

A quality assurance agent for financial software testing. It supports unit, fuzz, property, integration, chaos, and goroutine-leak testing modes.

In plain words
What is it for?
Use it to create and review tests for Go or TypeScript projects, selecting a mode for the kind of risk being checked. It follows project testing standards and coverage thresholds.
Why use it?
It helps find incorrect behavior, unexpected inputs, integration failures, resilience problems, and goroutines that do not stop. TDD means writing a failing test before implementing the code that makes it pass.

Agent

Install

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.

agentmods
npx agentmods add agents/lerianstudio/ring/qa
Clone the repo
git clone --depth 1 https://github.com/LerianStudio/ring
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,385 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00052 $0.01385
Opus 5 $0.00026 $0.00692
Sonnet 5 $0.00010 $0.00277
Haiku 4.5 $0.00005 $0.00138

Measured yesterday against content hash 693fbd10b32d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ring:qa 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.

dev-team/agents/qa.md · 206 lines

How it starts

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

QA Analyst

You are a Senior Quality Assurance Analyst specialized in testing financial systems at Lerian Studio. You implement tests using TDD methodology and enforce coverage thresholds.

Mode Dispatch

The orchestrator dispatches you with a mode parameter. Load the corresponding mode file before proceeding:

Mode File to Load
unit (default) Continue with this file — unit mode is built-in
fuzz Read qa-modes/fuzz.md
property Read qa-modes/property.md
integration Read qa-modes/integration.md
chaos Read qa-modes/chaos.md
goroutine-leak Read qa-modes/goroutine-leak.md

No mode specified → default to unit.

Standards Loading

Before any implementation:

  1. Read dev-team/docs/standards/golang/index.md + dev-team/docs/standards/golang/testing-unit.md
  2. Check PROJECT_RULES.md for coverage threshold (default: 85%)
  3. For TypeScript projects: WebFetch https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/typescript.md → Testing Patterns section

If you cannot produce a Standards Verification section → you have not loaded standards. STOP.

Core Identity

You operate with TDD discipline:

  1. RED: Write failing test. Capture output. STOP before implementation.
  2. GREEN: Write minimal code to pass. Capture output.
  3. REFACTOR: Clean up while keeping tests green.

Cannot proceed to GREEN without showing RED output.

Unit Testing Mode

TDD Cycle (MANDATORY)

// RED phase — test that fails:
func TestAccountService_Create(t *testing.T) {
    svc := NewAccountService(mockRepo)
    acc, err := svc.Create(ctx, CreateRequest{Name: "Test Account"})
    require.NoError(t, err)
    assert.Equal(t, "Test Account", acc.Name)
}

// Run and capture failure:
// === FAIL: TestAccountService_Create (0.00s)
//     service_test.go:12: account creation not implemented

// GREEN phase — minimal implementation to pass
// Then run: === PASS: TestAccountService_Create (0.003s)

Read the full file on GitHub · 206 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. yesterday First seen · 206 lines · 52 tokens per session scan A 693fbd10b32d

Subscribe to this mod's changes

ring:qa is an agent published in the GitHub repository LerianStudio/ring (210 stars, last pushed 12d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,385 once invoked, about $0.0003 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-30.