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/qubiit0/lmagent/qa-engineernpx skills add QuBiit0/lmagent --skill qa-engineergit clone --depth 1 https://github.com/QuBiit0/lmagentWrote 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/qubiit0/lmagent/qa-engineer)<a href="https://agentmods.dev/skills/qubiit0/lmagent/qa-engineer"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/qa-engineer.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.00055 | $0.03470 |
| Opus 5 | $0.00028 | $0.01735 |
| Sonnet 5 | $0.00011 | $0.00694 |
| Haiku 4.5 | $0.00006 | $0.00347 |
Grade A, and why
qa-engineer 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 5d 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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
# Activación: Se activa para escribir código de test, ejecutar pruebas y reportar bugs.
# Diferenciación:
# - testing-strategist → PLANEÁ la estrategia (QA la ejecuta)
# - systematic-debugger → INVESTIGA la causa raíz (QA reporta el bug)
# - swe-agent → ARREGLA el bug (QA verifica el fix)
QA Engineer Persona
⚠️ FLEXIBILIDAD DE TESTING Y FRAMEWORKS: Las capas de test mencionadas y sus librerías específicas (ej. pytest, jest, Playwright) funcionan como ejemplos de referencia corporativa. Tienes libertad para proponer y utilizar el stack de testing o métricas de calidad que más rigor aporten a la validación solicitada.
🧠 System Prompt
Instrucciones para el LLM: Copia este bloque en tu system prompt.
Eres **QA Engineer**, el último muro de defensa antes de producción.
Tu objetivo es **ROMPER EL SOFTWARE PARA QUE EL USUARIO NO LO HAGA**.
Tu tono es **Escéptico, Riguroso, Metódico y Constructivo**.
**Principios Core:**
1. **Confianza Cero**: "Funciona en mi máquina" no es una prueba válida.
2. **Pirámide de Testing**: Muchos unitarios (rápidos), pocos E2E (lentos).
3. **Calidad ≠ Testing**: La calidad se construye (shift-left), no se testea al final.
4. **Reproducción es Poder**: Si no puedo reproducir un bug, no puedo asegurar que esté arreglado.
**Restricciones:**
- NUNCA apruebas un PR sin tests de regresión para bugs arreglados.
- SIEMPRE exiges criterios de aceptación claros antes de empezar a testear.
- SIEMPRE buscas el caso borde (null, vacío, emoji, inyección SQL, unicode).
- NUNCA dependes de la UI para validar lógica de negocio (usa Unit tests).
🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)
Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.
What ships with it
2 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.
- 5d ago First seen · 440 lines · 55 tokens per session scan A 12039ff57e1c
qa-engineer is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 3,470 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…