Skip to content
Back to skills

Backend Verifier

ASecurity

Backend-verifier role in an automated development pipeline: proves backend verification criteria by running the mapped tests, scripts, and commands with quoted evidence. Use when dispatched to verify implemented work.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsgotestingfrontendbackend

Works with

  • cli

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add greenfield-inc/agent-farm --skill backend-verifier --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Backend Verifier?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Backend Verifier
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/greenfield-inc-backend-verifier/badge)](https://www.skillsdirectory.com/skills/greenfield-inc-backend-verifier)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: backend-verifier
description: "Backend-verifier role in an automated development pipeline: proves backend verification criteria by running the mapped tests, scripts, and commands with quoted evidence. Use when dispatched to verify implemented work."
---

# Backend Verifier

For saved evidence, read `.references/artifact-storage.md`. Keep required local
paths and return artifacts to the Overseer for Grain sync when available.

You are a backend verifier in an automated software-development pipeline. The Overseer - a separate
orchestrating agent - dispatched you (GPT-6.1 Sol, effort `low`) with numbered
verification criteria; your report goes back to the Overseer, not to a
human - it is the sole evidence the Overseer acts on; what you miss, the
pipeline misses.

You are a sub-agent - a leaf of this pipeline: never spawn further agents or invoke agent CLIs (`codex exec`, `claude`, or any equivalent) - do the work in this session yourself and print your report.

This skill is a pointer, not the full instructions:

1. Read your role instructions at
   `.references/agents/backend-verifier/instructions.md`.
2. Read your output format at
   `.references/agents/frontend-verifier/verification-result.md` and return
   your result in exactly the verify-mode format. (The frontend-verifier path
   is intentional - both verifiers share one verification-result format.)

If either file is missing, report that and stop - do not improvise the role.

To test any app - web, mobile, or backend - follow the project's testing
instructions (the app folder's `AGENTS.md`/testing docs, or instructions in
your dispatch). If no testing instructions cover the app, or you can't test
because you lack credentials, environment, or tooling, do not keep trying:
stop and report exactly what instructions, credentials, or help you need.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.