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/devrik99/forge-mcp/qa-masternpx skills add DevRik99/forge-mcp --skill qa-mastergit clone --depth 1 https://github.com/DevRik99/forge-mcpWrote 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/devrik99/forge-mcp/qa-master)<a href="https://agentmods.dev/skills/devrik99/forge-mcp/qa-master"><img src="https://agentmods.dev/badge/skills/devrik99/forge-mcp/qa-master.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.00171 | $0.22290 |
| Opus 5 | $0.00086 | $0.11145 |
| Sonnet 5 | $0.00034 | $0.04458 |
| Haiku 4.5 | $0.00017 | $0.02229 |
Grade A, and why
qa-master 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
14 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.
- _origen.json 244 B
- references/day1_onboarding.md 9.5 KB
- references/google_testing_standards.md 5.0 KB
- references/ground_truth_principle.md 9.8 KB
- references/llm_prompts_library.md 16 KB
- references/master_qa_prompt.md 12 KB
- references/TEST-CASE-TEMPLATE.md 4.4 KB
- REGLAS-DURAS.md 3.5 KB
- scripts/calculate_metrics.py 2.8 KB runs code
- scripts/init_qa_project.py 12 KB runs code
- templates/check-coverage-thresholds-per-file.mjs 2.5 KB runs code
- templates/check-feature-list-schema-check-wired.mjs 2.9 KB runs code
- templates/check-mutation-score-threshold.mjs 1.9 KB runs code
- templates/check-smoke-test-exists.mjs 2.8 KB runs code
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.
- 2d ago First seen · 2,304 lines · 171 tokens per session scan A 08c023af77f4
qa-master is a skill published in the GitHub repository DevRik99/forge-mcp (0 stars, last pushed 7d ago), with no licence file. It adds 171 tokens to every session and 22,290 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
test-strategist
This skill should be used when the user asks to "plan test strategy", "improve test coverage", "fix flaky tests", "optimize test performance", or needs guidance on testing infrastructure and quality assurance. Provides expert guidance on test strategy design, coverage analysis, and test quality improvement.
regression-test-gen
Suggest regression coverage for changed stack behavior.
test-fix
Automatically invoke when any test run produces failures. Triggers on: test output showing FAIL, test errors, or assertion failures in unit or E2E suites. Applies a strict 3-attempt limit per failure to avoid debugging spirals — stops and escalates if not resolved. Do NOT wait for user to ask; invoke immediately when…
test-master
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…