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/aigentive/ralphx/qa-evaluationnpx skills add aigentive/RalphX --skill qa-evaluationgit clone --depth 1 https://github.com/aigentive/RalphXWhat 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 | $0.00014 | $0.01056 |
| Opus 5 | $0.00007 | $0.00528 |
| Sonnet 5 | $0.00003 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
qa-evaluation 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Evaluation
Guidelines for refining test plans based on actual implementation and evaluating results.
Phase 2A: Refinement Process
1. Analyze Git Diff
git diff HEAD~1 --stat # Overview of changed files
git diff HEAD~1 -- <file> # Specific file changes
git log -1 --oneline # Commit message context
2. Compare Intent vs Reality
- Original acceptance criteria: What was planned
- Git diff: What was actually implemented
- Identify:
- Selectors that changed (testids, classes)
- Features added/removed
- UI structure differences
3. Refine Test Steps
Update test commands to match actual implementation:
- Correct element selectors
- Adjust wait times
- Update expected outcomes
- Add tests for new features
- Remove tests for dropped features
Refinement Output Format
{
"actual_implementation": "Brief summary of what git diff shows was implemented",
"refined_test_steps": [
{
"id": "QA1",
"criteria_id": "AC1",
"description": "Updated description",
"commands": [
"agent-browser open http://localhost:1420",
"agent-browser wait --load",
"agent-browser is visible [data-testid='actual-element']",
"agent-browser screenshot \"$RALPHX_AGENT_SCREENSHOT_DIR/qa1.png\""
],
"expected": "Updated expectation"
}
]
}
Phase 2B: Test Execution
Execution Flow
- Execute each test step in order
- Record pass/fail for each command
- Capture screenshot regardless of outcome
- Continue testing even if step fails
- Calculate overall status
Result Recording
For each step:
- status: "passed" | "failed" | "skipped"
- screenshot: Path to captured image
- actual: What actually happened (if failure)
- expected: What should have happened
- error: Error message (if any)
Test Results Output Format
{
"qa_results": {
"task_id": "task-123",
"overall_status": "passed",
"total_steps": 5,
"passed_steps": 5,
"failed_steps": 0,
"steps": [
{
"step_id": "QA1",
"status": "passed",
"screenshot": "$RALPHX_AGENT_SCREENSHOT_DIR/qa1-result.png",
"actual": null,
"expected": null,
"error": null
}
]
}
}
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 · 191 lines · 14 tokens per session scan A 368bcd7956ec
qa-evaluation is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,056 once invoked, about $0.0001 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…