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 Bilal140202/the-lord-of-the-skills --skill skyvern-ai__skyverngit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-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/bilal140202/the-lord-of-the-skills/skyvern-ai__skyvern)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/skyvern-ai__skyvern"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/skyvern-ai__skyvern/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/bilal140202/the-lord-of-the-skills/skyvern-ai__skyvern"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/skyvern-ai__skyvern.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.00033 | $0.03860 |
| Opus 5.5 | $0.00013 | $0.01544 |
| Sonnet 5.5 | $0.00007 | $0.00772 |
| Haiku 4.5 | $0.00003 | $0.00386 |
Grade A, and why
qa scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Use the repo's documented auth scheme and local base URL. Use `curl`, the repo SDK, or a small How it starts
The opening of the file, as written. The whole thing — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA — Validate Frontend and Backend Changes
Read the diff, classify what changed, and run the right validation path: browser QA for frontend/browser changes, API validation for backend surface changes, repo-native validation for backend-internal changes, and both for mixed changes.
You changed code. This skill is diff-driven first: it reads what changed, understands the affected behavior, and validates that behavior with the right tools. It is not a generic website crawler, and it should not invent random API checks that are unrelated to the diff.
Quick Start
/qa # Diff-based: choose the right validation path automatically
/qa http://localhost:3000 # Same, explicit frontend URL
/qa -- validate the workflow filters API
How It Works
- Read the code changes from
git diff - Read the changed files to understand behavior, routes, schemas, and UI
- Classify the diff as
frontend/browser,backend API,backend-internal, ormixed - Run the right validation flow
- Report pass/fail with concrete evidence
Step 1: Understand the Changes
Get the diff
# What files changed?
git diff --name-only HEAD~1 # vs last commit (if changes are committed)
git diff --name-only # vs working tree (if uncommitted)
# Full diff for context
git diff HEAD~1 # or git diff for uncommitted
Pick whichever diff has content. If both are empty, there is nothing diff-driven to QA.
Read the changed files
Read the full contents of every changed file that affects behavior:
- Frontend files:
.tsx,.jsx,.ts,.js,.css,.html - Backend/API files: routes, controllers, request/response schemas, serializers, handlers
- Backend-internal files: services, workers, business logic, validators, data-layer code
- Tests that changed alongside the implementation
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.
- 1mo ago First seen · 461 lines · 33 tokens per session scan A aeffd51bafd6
qa is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 3,860 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
qa-safe-healing
Diagnose Playwright and cross-layer application failures from repository evidence, then apply only policy-permitted repairs and targeted validation.
reliability
Use when user asks to stress-test the system, validate reconnection behavior, check for race conditions, or verify end-to-end data flow integrity.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
agent-debug-fixer
A Chinese-language debugging and repair workflow for software problems. It investigates errors, failed tests, broken pages, or behavior that does not match expectations, then makes a minimal fix.
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.