shift-right-testing

shift-right-testing is a skill for Claude Code from summarybotng/summarybot-ng. It costs 32 tokens per session (1,581 once invoked), scanned A, original, MIT.

A guide to testing software after it reaches production, using controlled releases, monitoring, and deliberate failure checks. A canary release sends a new version to a small group first, while synthetic monitoring simulates user activity.

In plain words
What is it for?
Use it for progressive feature rollouts, production reliability checks, performance monitoring, or chaos-engineering exercises.
Why use it?
It helps teams detect problems in real usage and limit the impact of a faulty release. It also provides ways to learn from production behavior and test system resilience.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it for progressive feature rollouts, production reliability checks, performance monitoring, or chaos-engineering exercises.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/summarybotng/summarybot-ng/shift-right-testing
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.

Any agent
npx skills add summarybotng/summarybot-ng --skill shift-right-testing
Clone the repo
git clone --depth 1 https://github.com/summarybotng/summarybot-ng

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 shift-right-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/shift-right-testing/github.svg)](https://agentmods.dev/skills/summarybotng/summarybot-ng/shift-right-testing)
Your own site
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/shift-right-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/shift-right-testing/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 shift-right-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/shift-right-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/shift-right-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,581 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.00032 $0.01581
Opus 5 $0.00016 $0.00790
Sonnet 5 $0.00006 $0.00316
Haiku 4.5 $0.00003 $0.00158

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

Security

Grade A, and why

shift-right-testing 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.

.claude/skills/shift-right-testing/SKILL.md · 234 lines

How it starts

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

Shift-Right Testing

<default_to_action> When testing in production or implementing progressive delivery:

  1. IMPLEMENT feature flags for progressive rollout (1% → 10% → 50% → 100%)
  2. DEPLOY with canary releases (compare metrics before full rollout)
  3. MONITOR with synthetic tests (proactive) + RUM (reactive)
  4. INJECT failures with chaos engineering (build resilience)
  5. ANALYZE production data to improve pre-production testing

Quick Shift-Right Techniques:

  • Feature flags → Control who sees what, instant rollback
  • Canary deployment → 5% traffic, compare error rates
  • Synthetic monitoring → Simulate users 24/7, catch issues before users
  • Chaos engineering → Netflix-style failure injection
  • RUM (Real User Monitoring) → Actual user experience data

Critical Success Factors:

  • Production is the ultimate test environment
  • Ship fast with safety nets, not slow with certainty
  • Use production data to improve shift-left testing </default_to_action>

Quick Reference Card

When to Use

  • Progressive feature rollouts
  • Production reliability validation
  • Performance monitoring at scale
  • Learning from real user behavior

Shift-Right Techniques

Technique Purpose When
Feature Flags Controlled rollout Every feature
Canary Compare new vs old Every deployment
Synthetic Monitoring Proactive detection 24/7
RUM Real user metrics Always on
Chaos Engineering Resilience validation Regularly
A/B Testing User behavior validation Feature decisions

Progressive Rollout Pattern

1% → 10% → 25% → 50% → 100%
↓      ↓      ↓      ↓
Check  Check  Check  Monitor

Key Metrics to Monitor

Metric SLO Target Alert Threshold
Error rate < 0.1% > 1%
p95 latency < 200ms > 500ms
Availability 99.9% < 99.5%
Apdex > 0.95 < 0.8

Feature Flags

// Progressive rollout with LaunchDarkly/Unleash pattern
const newCheckout = featureFlags.isEnabled('new-checkout', {
  userId: user.id,
  percentage: 10,  // 10% of users
  allowlist: ['beta-testers']
});

if (newCheckout) {
  return <NewCheckoutFlow />;
} else {
  return <LegacyCheckoutFlow />;
}

// Instant rollback on issues
await featureFlags.disable('new-checkout');

Read the full file on GitHub · 234 lines

Files

What ships with it

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

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. 5d ago First seen · 234 lines · 32 tokens per session scan A 899fbfd62eba

Subscribe to this mod's changes

shift-right-testing is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,581 once invoked, about $0.0002 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-09-03.