agent-production-validator

agent-production-validator is a skill for Claude Code from proffesor-for-testing/agentic-qe. It costs 16 tokens per session (2,690 once invoked), scanned A, a copy of agent-production-validator, MIT.

A software validation helper that checks whether an application is fully implemented and ready for deployment. It focuses on real implementations, end-to-end tests, and deployment readiness.

In plain words
What is it for?
Use it to inspect source code, look for placeholder implementations, run production or end-to-end tests when available, and simulate real-world validation.
Why use it?
It helps expose unfinished mock, fake, stub, TODO, or FIXME code before an application is treated as production-ready.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

Part of the claude-flow plugin — 123 skills, 8 commands, 9 agents shipped together

Good fit Use it to inspect source code, look for placeholder implementations, run production or end-to-end tests when available, and simulate real-world validation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/proffesor-for-testing/agentic-qe/agent-production-validator
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 proffesor-for-testing/agentic-qe --skill agent-production-validator
Clone the repo
git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 123 skills, 8 commands, 9 agents.

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/proffesor-for-testing/agentic-qe/agent-production-validator/github.svg)](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-production-validator)
Your own site
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-production-validator"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-production-validator/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 agent-production-validator

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-production-validator"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-production-validator.svg" alt="Reviewed on agentmods" width="80" 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. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.5 $0.00006 $0.01076
Sonnet 5.5 $0.00003 $0.00538
Haiku 4.5 $0.00002 $0.00269

Measured 1mo ago against content hash ce83025ab317, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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

This is a copy

100% identical to agent-production-validator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/ruflo/.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. 1mo 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 proffesor-for-testing/agentic-qe (508 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 2,690 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-production-validator, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens