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 skills add vaquarkhan/Fullstack-development-agent-skills --skill fullstack-testing-and-quality-gatesgit clone --depth 1 https://github.com/vaquarkhan/Fullstack-development-agent-skillsWrote 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/vaquarkhan/fullstack-development-agent-skills/fullstack-testing-and-quality-gates)<a href="https://agentmods.dev/skills/vaquarkhan/fullstack-development-agent-skills/fullstack-testing-and-quality-gates"><img src="https://agentmods.dev/badge/skills/vaquarkhan/fullstack-development-agent-skills/fullstack-testing-and-quality-gates/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/skills/vaquarkhan/fullstack-development-agent-skills/fullstack-testing-and-quality-gates"><img src="https://agentmods.dev/badge/skills/vaquarkhan/fullstack-development-agent-skills/fullstack-testing-and-quality-gates.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.00037 | $0.00559 |
| Opus 5.5 | $0.00015 | $0.00224 |
| Sonnet 5.5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
fullstack-testing-and-quality-gates 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fullstack Testing And Quality Gates
Use When
- New fullstack features are being delivered
- Teams need predictable pre-merge and pre-release gates
- Regressions occur between frontend and backend integration points
Workflow
- Map risk by feature area, user path, and service dependency.
- Define layered tests: unit, component, contract, integration, and end-to-end.
- Prioritize deterministic tests for core flows and flaky-test elimination.
- Build CI gates for linting, type checks, tests, coverage thresholds, and security checks.
- Add release smoke tests for production-like environments.
- Capture evidence and failure triage guidance in pull request templates.
Test Coverage Model
- Unit tests for domain rules and utility logic
- Component tests for UI state transitions and accessibility behavior
- Contract tests for request and response compatibility
- Integration tests for API, database, and queue boundaries
- End-to-end tests for critical business journeys only
Required Checks
- Contract changes include backward compatibility or migration note
- Coverage thresholds exist for changed modules
- Flaky tests are quarantined with an owner and remediation date
- CI failures include actionable logs and reproduction steps
Decision Framework
- Map tests to risk: unit for rules, contract for APIs, integration for boundaries, E2E only for revenue-critical journeys.
- Block merge on lint, typecheck, unit, and contract suites; gate release on smoke and migration compatibility tests.
- Quarantine flaky tests with owner and SLA; never silently retry without tracking flake rate.
- Require backward-compatibility proof when contracts or schemas change.
Common Rationalizations And Rebuttals
- "E2E covers everything." -> E2E is slow and brittle; lean on contracts and integration for breadth.
- "Coverage percentage is the goal." -> Covered nonsense tests provide false confidence; assert behavior and contracts.
- "We can skip gates for hotfixes." -> Hotfixes cause most regressions; expedite with scoped gates, don't remove them.
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.
- 1mo ago First seen · 64 lines · 37 tokens per session scan A 00ec012956fe
fullstack-testing-and-quality-gates is a skill published in the GitHub repository vaquarkhan/Fullstack-development-agent-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 559 once invoked, about $0.0001 per session on Opus 5.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-07.
Other skills, from other repositories
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…
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
cometchat-flutter-v6-testing
Test a Flutter app that uses the CometChat UI Kit — what is worth testing versus what belongs to the kit, mocking the SDK boundary, widget tests around chat screens, and integration/CI setup. Triggers: 'test my cometchat integration', 'mock cometchat in flutter tests', 'widget test chat screen', 'cometchat test setup'.
cometchat-ios-testing
Test an iOS app that embeds CometChat — what to mock vs exercise for real, keeping the CometChatSDK off the network in unit tests, waiting out the async init→login gate, and a lean XCUITest smoke. Triggers: 'test cometchat ios', 'unit test chat swift', 'mock cometchatsdk', 'xcuitest for chat', 'how do I test cometchat…
verify
Verification loop — lint -> typecheck -> unit -> integration -> e2e.
flutter-testing
Use when testing Flutter code - unit tests for logic, widget tests for UI behavior, golden tests for appearance, the multi-size/text-scale/dark matrix, accessibility guidelines, test-first.