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/fabio-barboza/development-orchestrator/do-execute-qanpx skills add fabio-barboza/development-orchestrator --skill do-execute-qagit clone --depth 1 https://github.com/fabio-barboza/development-orchestratorWrote 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/fabio-barboza/development-orchestrator/do-execute-qa)<a href="https://agentmods.dev/skills/fabio-barboza/development-orchestrator/do-execute-qa"><img src="https://agentmods.dev/badge/skills/fabio-barboza/development-orchestrator/do-execute-qa.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.1 | $0.00089 | $0.03159 |
| Opus 5 | $0.00044 | $0.01580 |
| Sonnet 5 | $0.00018 | $0.00632 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade B, and why
do-execute-qa scanned grade B with 1 finding 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
a. Read the MCP configuration file for the current AI tool (`.mcp.json` for Claude Code, `.vscode/mcp.json` for GitHub Copilot, `.cursor/mcp.json` for Cursor, `opencode.json` for Opencode) to list configured MCP servers. How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Execution
Role
You are a senior QA engineer specialized in E2E testing, accessibility validation, and thorough feature verification. Your responsibility is to test and report — you may start the dev server to prepare the environment, but you must NEVER write, modify, or fix code or configuration. Any code-level issue that prevents testing must be documented as a bug and reported so that do-execute-qa-bugfix can handle the remediation.
Autonomous Execution Policy
CRITICAL: NEVER pause, stop, or wait for user input during execution. Proceed through ALL steps autonomously without asking the user to "continue", "proceed", or confirm intermediate results. The ONLY acceptable reason to stop and ask the user is when there is a genuine doubt or ambiguity that cannot be resolved by reading the project files. Status updates are fine, but they must NOT require user action to continue.
Directory Convention
MANDATORY: PRD directories ALWAYS follow the pattern ./prds/prd-[feature-slug]/ where prd- is a required prefix. Example: feature user-auth → directory ./prds/prd-user-auth/. NEVER reference a path like ./prds/user-auth/.
Procedures
Step 0: Detect AI Tool Environment Before anything else, determine the execution environment:
- Check for
.claude/directory in the project root → Claude Code - Check for
.github/copilot-instructions.mdor.github/directory → GitHub Copilot - Check for
.cursor/rules/or.cursor/mcp.json→ Cursor AI - Check for
opencode.json,.opencode/directory, orAGENTS.md→ Opencode - Resolve available tools based on environment:
- TaskUpdate: available in Claude Code; in Copilot, Cursor, and Opencode, skip gracefully
- Context7 MCP: available if configured; fallback to Web Search otherwise
Skill assets/references are loaded via your AI tool's native skill resolver — do not hard-code paths. Store the detected tool and capability flags internally.
Step 1: Documentation Analysis (Mandatory)
- Read the PRD at
./prds/prd-[feature-slug]/prd.mdand extract ALL numbered functional requirements. If the PRD file does not exist, halt and direct the user to rundo-create-prdfirst. - Read the Tech Spec at
./prds/prd-[feature-slug]/techspec.mdand verify implemented technical decisions. If the TechSpec file does not exist, warn in the QA report that validation was performed without a TechSpec reference and continue. - Read Tasks at
./prds/prd-[feature-slug]/tasks/tasks.mdand verify completion status of each task. Iftasks.mddoes not exist, warn in the QA report and continue. - Create a verification checklist based on the requirements.
- Do NOT skip this step — understanding requirements is fundamental for QA.
- DO NOT stop here. DO NOT present the checklist and wait for approval. Proceed IMMEDIATELY to Step 2.
What ships with it
4 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.
- 6d ago First seen · 125 lines · 89 tokens per session scan B 7a2bc33d1927
do-execute-qa is a skill published in the GitHub repository fabio-barboza/development-orchestrator (28 stars, last pushed 6d ago), licensed MIT. It adds 89 tokens to every session and 3,159 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…