Borrowing it
Nothing to install: this file belongs to julianobarbosa/azure-finops-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/julianobarbosa/azure-finops-mcp-server/main/.claude/commands/BMad/tasks/apply-qa-fixes.mdgit clone --depth 1 https://github.com/julianobarbosa/azure-finops-mcp-serverWrote 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/commands/julianobarbosa/azure-finops-mcp-server/apply-qa-fixes)<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/apply-qa-fixes"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/apply-qa-fixes/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.
<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/apply-qa-fixes"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/apply-qa-fixes.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01409 |
| Opus 5 | $0.00000 | $0.00705 |
| Sonnet 5 | $0.00000 | $0.00282 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
apply-qa-fixes 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 10d 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.
This is a copy
100% identical to apply-qa-fixes — 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/apply-qa-fixes Task
When this command is used, execute the following task:
apply-qa-fixes
Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
Purpose
- Read QA outputs for a story (gate YAML + assessment markdowns)
- Create a prioritized, deterministic fix plan
- Apply code and test changes to close gaps and address issues
- Update only the allowed story sections for the Dev agent
Inputs
required:
- story_id: '{epic}.{story}' # e.g., "2.2"
- qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
- story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
optional:
- story_title: '{title}' # derive from story H1 if missing
- story_slug: '{slug}' # derive from title (lowercase, hyphenated) if missing
QA Sources to Read
- Gate (YAML):
{qa_root}/gates/{epic}.{story}-*.yml- If multiple, use the most recent by modified time
- Assessments (Markdown):
- Test Design:
{qa_root}/assessments/{epic}.{story}-test-design-*.md - Traceability:
{qa_root}/assessments/{epic}.{story}-trace-*.md - Risk Profile:
{qa_root}/assessments/{epic}.{story}-risk-*.md - NFR Assessment:
{qa_root}/assessments/{epic}.{story}-nfr-*.md
- Test Design:
Prerequisites
- Repository builds and tests run locally (Deno 2)
- Lint and test commands available:
deno lintdeno test -A
Process (Do not skip steps)
0) Load Core Config & Locate Story
- Read
bmad-core/core-config.yamland resolveqa_rootandstory_root - Locate story file in
{story_root}/{epic}.{story}.*.md- HALT if missing and ask for correct story id/path
1) Collect QA Findings
- Parse the latest gate YAML:
gate(PASS|CONCERNS|FAIL|WAIVED)top_issues[]withid,severity,finding,suggested_actionnfr_validation.*.statusand notestracecoverage summary/gapstest_design.coverage_gaps[]risk_summary.recommendations.must_fix[](if present)
- Read any present assessment markdowns and extract explicit gaps/recommendations
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.
- 10d ago First seen · 155 lines · 0 tokens per session scan A 0429d07ca661
apply-qa-fixes is a command published in the GitHub repository julianobarbosa/azure-finops-mcp-server (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,409 tokens. A static security scan graded it A with 0 findings. It is 100% identical to apply-qa-fixes, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.