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/stuartshields/claude-setup/qa-checknpx skills add stuartshields/claude-setup --skill qa-checkgit clone --depth 1 https://github.com/stuartshields/claude-setupWhat 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.00041 | $0.03816 |
| Opus 5 | $0.00020 | $0.01908 |
| Sonnet 5 | $0.00008 | $0.00763 |
| Haiku 4.5 | $0.00004 | $0.00382 |
Grade A, and why
qa-check 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- No `eval()`, `Function()`, or `child_process.exec()` with user input. How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: qa-check (Global)
When to Use
Run /qa-check on any web project to audit for Accessibility (WCAG 2.2 AA), Performance, and Code Quality issues. This skill auto-detects the tech stack and adapts its checks accordingly.
Use $ARGUMENTS to scope the audit to a specific directory or file pattern (e.g., /qa-check src/components/). If empty, audit the entire project.
Do NOT fix issues - only report them. Present findings as structured Markdown tables.
Method
Phase 0: Stack Detection
Before running any checks, detect the project's tech stack by scanning the working directory for marker files. Report what was detected before proceeding.
Detection Rules
Scan in this order. A project can match multiple stacks (e.g., WordPress with Node build tools).
| Stack | Marker Files |
|---|---|
| WordPress / PHP | wp-config.php, composer.json with "wordpress", style.css containing Theme Name:, functions.php, wp-content/ or content/ directory |
| Python | requirements.txt, pyproject.toml, setup.py, setup.cfg, Pipfile, manage.py (Django), app.py or wsgi.py (Flask) |
| Node / JS | package.json - then inspect for framework indicators: next (Next.js), express (Express), nuxt (Nuxt), @angular/core (Angular), react (React), vue (Vue), svelte (Svelte) |
| Static Web | *.html files in root or src/, *.css files, no backend markers detected |
Detection Output
Print a summary before running checks:
## Stack Detection
| Stack | Detected | Markers Found |
|---|---|---|
| WordPress/PHP | Yes/No | wp-config.php, style.css (Theme Name: ...) |
| Python | Yes/No | requirements.txt, manage.py |
| Node/JS | Yes/No | package.json (express, react) |
| Static Web | Yes/No | index.html, styles.css |
Then determine which template/view files to scan:
- WordPress:
*.phpin theme directory,template-parts/,templates/,inc/ - Python (Flask):
templates/**/*.html,app/templates/**/*.html - Python (Django):
**/templates/**/*.html,**/templatetags/*.py - Node (Next.js):
pages/**/*.{js,jsx,tsx},app/**/*.{js,jsx,tsx},components/**/*.{js,jsx,tsx} - Node (Express):
views/**/*.{ejs,pug,hbs,html},public/**/*.html - Node (React/Vue/Svelte):
src/**/*.{jsx,tsx,vue,svelte} - Static Web:
*.html,src/**/*.html
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 · 266 lines · 41 tokens per session scan A 0fee6abc79ce
qa-check is a skill published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 3,816 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memory
Claude Mind - Search and manage Claude's persistent memory stored in a single portable .mv2 file.
bearing-diagnosis
Complete bearing fault diagnostic workflow using vibration analysis and the predictive-maintenance-mcp server. Use this skill when the user says "diagnose bearing", "bearing fault", "bearing check", "detect bearing damage", "bearing vibration analysis", "inner race fault", "outer race fault", "ball defect", "cage…
prognostics
Prognostic assessment workflow: trend analysis, degradation onset detection, and Remaining Useful Life (RUL) estimation using the predictive-maintenance-mcp server. Use this skill when the user says "trend analysis", "degradation trend", "RUL", "remaining useful life", "prognosis", "prognostics", "failure prediction"…
signal-management
Signal loading, generation, and cache management using the predictive-maintenance-mcp server. Use this skill when the user says "load signal", "import signal", "list signals", "available signals", "generate test signal", "create test data", "synthetic signal", "clear cache", "signal info", "what signals are loaded"…
anomaly-detection
ML-based anomaly detection and model training for vibration signals using the predictive-maintenance-mcp server. Use this skill when the user says "anomaly detection", "train model", "detect anomalies", "outlier detection", "normal vs abnormal", "machine learning", "one-class SVM", "LOF", "local outlier factor"…
gear-diagnosis
Gear fault diagnosis workflow using vibration analysis via the predictive-maintenance-mcp server. Use this skill when the user says "gear fault", "gear diagnosis", "gear mesh", "gearbox analysis", "gear vibration", "tooth damage", "gear defect", "diagnose gear", "gear mesh frequency", "sideband analysis", or wants to…