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 HirogaKatageri/hirokata --skill qa-artifactsgit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/hirogakatageri/hirokata/qa-artifacts)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/qa-artifacts"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/qa-artifacts/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/hirogakatageri/hirokata/qa-artifacts"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/qa-artifacts.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.00137 | $0.03820 |
| Opus 5 | $0.00068 | $0.01910 |
| Sonnet 5 | $0.00027 | $0.00764 |
| Haiku 4.5 | $0.00014 | $0.00382 |
Grade A, and why
qa-artifacts 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 today.
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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Artifacts — What Is a Row, What Is Prose
QA produces four kinds of output, and two of them are database rows. That is the whole
point of this skill: a defect written into a markdown file is invisible to v_brief, to the
dashboard's Bugs view, to v_open_bugs, and to every human who looks at the board — so the
record has to live where the board can see it. The care you put into describing the defect
does not change. Only where it lands.
Load guild:warehouse before writing any of the SQL below. Every free-text value on this
page — a bug title, a repro, a coverage note — crosses as CAST(x'<hex>' AS TEXT), because a
repro step ending in ; at end of line tears the statement in half.
| Output | Lives in | Written by |
|---|---|---|
| A defect | the bug table |
qa-tester |
| A quality area + its risk + its spec | the coverage table |
qa-strategist plans, qa-tester stamps |
| Quality definition, oracle ledger | .guild/qa/charter.md |
qa-strategist |
| A mission (scope, journeys, what-if matrix) | .guild/qa/missions/MISSION-{slug}.md |
qa-strategist |
| A session log (what was run, what happened) | .guild/qa/sessions/SESSION-{slug}-{date}.md |
qa-tester |
| The committed-spec index | .guild/qa/regression.md |
qa-tester |
There is no .guild/qa/ledger.md. Bugs are rows.
.guild/qa/ remains evergreen — like the doc and coverage tables, these files outlive any
one board. Nothing in the guild deletes them, and nothing deletes the rows either (G11); a fresh
board is a fresh database file and .guild/qa/ carries straight across. Committed test specs do
NOT live here; they live in the project's real e2e dir and run in CI.
.guild/qa/
charter.md # qa-strategist: what quality means + where the oracle comes from
missions/ # qa-strategist: one MISSION-{slug}.md per quality area
sessions/ # tester: one SESSION-{slug}-{date}.md per run
regression.md # tester: index of committed specs in the repo
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.
- today Changed 78e9b73ccac4
- 5d ago Changed · +180 lines · +18 tokens per session d694c8555def
- 9d ago First seen · 159 lines · 119 tokens per session scan A 697ed5f761b0
qa-artifacts is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 3,820 once invoked, about $0.0007 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
self-test
A post-coding self-check checklist for reviewing implementation quality and tests. It checks user-visible behavior, data consistency, dependencies, compatibility, code quality, and—when relevant—visual details against a design.
implement
A coding method based on vertical slices: each slice connects the data, interface, display, and tests for one complete path. With a test framework, it follows TDD, meaning tests are written before the smallest implementation and then the code is cleaned up.
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.