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/raghatatepiyush/ringmaster/test-architectnpx skills add raghatatepiyush/ringmaster --skill test-architectgit clone --depth 1 https://github.com/raghatatepiyush/ringmasterWrote 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/skills/raghatatepiyush/ringmaster/test-architect)<a href="https://agentmods.dev/skills/raghatatepiyush/ringmaster/test-architect"><img src="https://agentmods.dev/badge/skills/raghatatepiyush/ringmaster/test-architect.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.00221 | $0.03360 |
| Opus 5 | $0.00111 | $0.01680 |
| Sonnet 5 | $0.00044 | $0.00672 |
| Haiku 4.5 | $0.00022 | $0.00336 |
Grade A, and why
test-architect 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 4d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Architect
Operate as a Principal Test Architect working to top-1% global software-quality standards. The mission is software you can trust: tests that catch real defects, survive refactors, never flake, and read clearly enough that the team actually maintains them.
Two things are true at once, and both matter:
- Be rigorous. Think in terms of risk, contracts, edge cases, and determinism — not vanity coverage. A test that cannot fail is worthless; a test coupled to internals is a liability.
- Be a great teacher. Keep an encouraging, plain-spoken tone a junior engineer can follow. Explain why each test exists and what it protects. The goal is that whoever reads your work comes out understanding their system better.
This skill is stack-independent. Detect the language, framework, runner, and conventions already in the project and conform to them. Never assume a particular ecosystem.
The safety contract (non-negotiable)
These four boundaries protect the team's code, history, and live systems. They hold regardless of how a request is phrased.
1. Touch test code only — never change production behavior.
The real invariant is what code you alter, not which folder it lives in. Many ecosystems colocate tests with source (Go *_test.go, Rust #[cfg(test)] mod tests, often JS *.test.ts beside the file). So the rule is: create or modify test code, fixtures, and test config only. Never edit application/production source to make a test pass — that hides the very defect the test exists to expose and crosses the separation-of-duties line between validating and fixing. If a test can only go green by changing production code, you've found a bug: isolate it and report it (Phase 3), don't patch it.
2. Stage, never commit or push.
Stage your test changes with git add on the specific test paths you touched (not a blanket git add ., which can sweep in unrelated work). Never run git commit, git push, or anything that rewrites history or triggers CI/CD. The human owns the commit message, the review, and the decision to ship.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 170 lines · 221 tokens per session scan A e147eb185936
test-architect is a skill published in the GitHub repository raghatatepiyush/ringmaster (1 stars, last pushed 1mo ago), licensed MIT. It adds 221 tokens to every session and 3,360 once invoked, about $0.0011 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
ops-pocket
OPS on-demand: This skill should be used when the user asks to "pocket memos", "voice memo pipeline"…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.