agent-production-validator

agent-production-validator is a skill for Claude Code, Codex from ruvnet/ruflo. It costs 16 tokens per session (2,690 once invoked), scanned A, original, MIT.

A coding-agent skill for checking whether an application is fully implemented and ready to deploy. It looks for unfinished placeholders and runs available production or end-to-end tests.

In plain words
What is it for?
Verifying implementation completeness, scanning source for unfinished markers, running production tests, running end-to-end tests, and assessing deployment readiness.
Why use it?
It helps reveal mock, fake, stub, or unfinished code and checks whether the real application behaves correctly in broader tests.

Skill for Claude CodeCodex

Part of the claude-flow plugin — 134 skills, 52 commands, 11 agents, 4 hooks shipped together

About the project

Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.

ruvnet/ruflo · 70,498 stars · on GitHub · cognitum.one

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 skills/ruvnet/ruflo/agent-production-validator
Any agent
npx skills add ruvnet/ruflo --skill agent-production-validator
Clone the repo
git clone --depth 1 https://github.com/ruvnet/ruflo

Made for: Claude Code, Codex.

Or install claude-flow, the plugin that ships this one along with the rest of its 134 skills, 52 commands, 11 agents, 4 hooks.

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 agent-production-validator

README.md
[![agentmods](https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-production-validator.svg)](https://agentmods.dev/skills/ruvnet/ruflo/agent-production-validator)
Your own site
<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-production-validator"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-production-validator.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,690 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.1 $0.00016 $0.02690
Opus 5 $0.00008 $0.01345
Sonnet 5 $0.00003 $0.00538
Haiku 4.5 $0.00002 $0.00269

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

Security

Grade A, and why

agent-production-validator 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 6d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.agents/skills/agent-production-validator/SKILL.md · 400 lines

How it starts

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


name: production-validator type: validator color: "#4CAF50" description: Production validation specialist ensuring applications are fully implemented and deployment-ready capabilities:

  • production_validation
  • implementation_verification
  • end_to_end_testing
  • deployment_readiness
  • real_world_simulation priority: critical hooks: pre: | echo "🔍 Production Validator starting: $TASK"

    Verify no mock implementations remain

    echo "🚫 Scanning for mock$fake implementations..." grep -r "mock|fake|stub|TODO|FIXME" src/ || echo "✅ No mock implementations found" post: | echo "✅ Production validation complete"

    Run full test suite against real implementations

    if [ -f "package.json" ]; then npm run test:production --if-present npm run test:e2e --if-present fi

Production Validation Agent

You are a Production Validation Specialist responsible for ensuring applications are fully implemented, tested against real systems, and ready for production deployment. You verify that no mock, fake, or stub implementations remain in the final codebase.

Core Responsibilities

  1. Implementation Verification: Ensure all components are fully implemented, not mocked
  2. Production Readiness: Validate applications work with real databases, APIs, and services
  3. End-to-End Testing: Execute comprehensive tests against actual system integrations
  4. Deployment Validation: Verify applications function correctly in production-like environments
  5. Performance Validation: Confirm real-world performance meets requirements

Validation Strategies

1. Implementation Completeness Check

// Scan for incomplete implementations
const validateImplementation = async (codebase: string[]) => {
  const violations = [];
  
  // Check for mock implementations in production code
  const mockPatterns = [
    $mock[A-Z]\w+$g,           // mockService, mockRepository
    $fake[A-Z]\w+$g,           // fakeDatabase, fakeAPI
    $stub[A-Z]\w+$g,           // stubMethod, stubService
    /TODO.*implementation$gi,   // TODO: implement this
    /FIXME.*mock$gi,           // FIXME: replace mock
    $throw new Error\(['"]not implemented$gi
  ];
  
  for (const file of codebase) {
    for (const pattern of mockPatterns) {
      if (pattern.test(file.content)) {
        violations.push({
          file: file.path,
          issue: 'Mock$fake implementation found',
          pattern: pattern.source
        });
      }
    }
  }
  
  return violations;
};

Read the full file on GitHub · 400 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. 6d ago First seen · 400 lines · 16 tokens per session scan A ce83025ab317

Subscribe to this mod's changes

agent-production-validator is a skill published in the GitHub repository ruvnet/ruflo (70,498 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 2,690 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-30.

Related

Other skills, from other repositories

nw-ad-critique-dimensions

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof.

nWave-ai/nWave · 53 tokens

nw-bdd-methodology

BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation.

nWave-ai/nWave · 36 tokens

external-memory-plugin

Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an…

ModelEngine-Group/nexent · 85 tokens

moai-ref-testing-pyramid

Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.

modu-ai/moai-adk · 61 tokens

nw-design

Designs system architecture with C4 diagrams and technology selection. Routes to the right architect based on design scope (system, domain, application, or full stack). Two interaction modes: guide (collaborative Q&A) or propose (architect presents options with trade-offs).

nWave-ai/nWave · 57 tokens

compare-harnesses

Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.

ruvnet/metaharness · 66 tokens