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/jaichangpark/workshop-harness/workshop-testernpx skills add JAICHANGPARK/workshop-harness --skill workshop-testergit clone --depth 1 https://github.com/JAICHANGPARK/workshop-harnessWrote 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/jaichangpark/workshop-harness/workshop-tester)<a href="https://agentmods.dev/skills/jaichangpark/workshop-harness/workshop-tester"><img src="https://agentmods.dev/badge/skills/jaichangpark/workshop-harness/workshop-tester.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.00034 | $0.00496 |
| Opus 5 | $0.00017 | $0.00248 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
workshop-tester 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 6d 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.
What it actually says
Workshop Tester Skill
Purpose
Catches broken code, missing files, broken markdown relative links, missing images, and dead HTTP URLs before the workshop goes live. Prevents attendees from running into preventable setup errors or dead links during live sessions.
3-Stage Automated Test Pipeline
[Stage 1: Code Smoke Test] -> [Stage 2: Markdown Link & Image Integrity Audit] -> [Stage 3: TODO Alignment Audit]
Stage 1: Code Smoke Tests
01_starter/Verification: Verify dependencies install cleanly and entry point (main.py/run.sh) executes without syntax or import errors.02_final/Verification: Run reference solution end-to-end and confirm expected terminal output and non-zero exit codes.- Environment Scripts: Run
scripts/check_env.shandscripts/check_architecture_compat.shto ensure execution without errors.
Stage 2: Markdown Link & Image Integrity Audit
- Scan all
.mdfiles indocs/,workshop/, and repository root for relative file links ([text](./path/to/file.md)). - Verify that every referenced target file exists on disk.
- Scan for embedded image links (
) and confirm image files exist in specified paths. - Flag dead external HTTP URLs (404 / 500 errors).
Stage 3: Starter vs Final TODO Alignment Audit
- Scan
workshop/01_starter/for all# TODO: [Lab N]markers. - Verify that every marked TODO item has a corresponding completed solution in
workshop/02_final/.
CLI Command Integration
Run the full integrity audit suite via harness_cli.py:
uv run harness_cli.py test --target my-bwai-workshop
Output Artifact & CI Integration
- Output: Detailed pass/fail test report printed to stdout with explicit error line numbers and broken file paths.
- Exit Code: Returns
0on 100% pass; returns1on any broken link or code failure for CI/CD workflow enforcement.
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.
- 6d ago First seen · 50 lines · 34 tokens per session scan A 3850f457c80c
workshop-tester is a skill published in the GitHub repository JAICHANGPARK/workshop-harness (5 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 496 once invoked, about $0.0002 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.