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 iamvonpasion/hashb --skill qagit clone --depth 1 https://github.com/iamvonpasion/hashbWrote 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/iamvonpasion/hashb/qa)<a href="https://agentmods.dev/skills/iamvonpasion/hashb/qa"><img src="https://agentmods.dev/badge/skills/iamvonpasion/hashb/qa/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/iamvonpasion/hashb/qa"><img src="https://agentmods.dev/badge/skills/iamvonpasion/hashb/qa.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.00018 | $0.02360 |
| Opus 5.5 | $0.00007 | $0.00944 |
| Sonnet 5.5 | $0.00004 | $0.00472 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade C, and why
qa scanned grade C 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- **Never refuse to use the browser.** Even if changes look backend-only, The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 298 lines · 18 tokens per session scan C cf8440e7a7ce
qa is a skill published in the GitHub repository iamvonpasion/hashb (2 stars, last pushed 5mo ago), with no licence file. It adds 18 tokens to every session and 2,360 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). 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
Entry point for bug fixes. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Domain-knowledge-driven root cause analysis.
tdd
Use when implementing any feature or bugfix, before writing implementation code. Risk-aware TDD with ecw.yml integration.
cypress-debugger
Use when a Cypress end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Cypress spec, Timed-out-retrying command, unresolved selector, cy.intercept alias or request race, suite-breaking hook, retry-only flake, hydration or timing race, or a…
playwright-debugger
Use when a Playwright end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Playwright spec, TimeoutError, broken or ambiguous selector, post-deploy suite failure, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split.…
diagnose
For a bug-fix brief, a bug resisting its first fix, or a fix about to ship without a proven cause, reproduce the failure, state its cause with evidence, and keep a regression check before shipping.
implement
For a build brief, implementing a spec or tracked item, or mid-build discoveries tempting scope expansion, build thin verified slices with test-first checks at named boundaries, proportional validation elsewhere, and respect for scope and commit instructions.