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/hiai-gg/hiai-opencode/generalnpx skills add HiAi-gg/hiai-opencode --skill generalgit clone --depth 1 https://github.com/HiAi-gg/hiai-opencodeWrote 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/hiai-gg/hiai-opencode/general)<a href="https://agentmods.dev/skills/hiai-gg/hiai-opencode/general"><img src="https://agentmods.dev/badge/skills/hiai-gg/hiai-opencode/general.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.00021 | $0.04611 |
| Opus 5 | $0.00010 | $0.02305 |
| Sonnet 5 | $0.00004 | $0.00922 |
| Haiku 4.5 | $0.00002 | $0.00461 |
Grade A, and why
systematic-debugging 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- condition-based-waiting-example.ts 4.9 KB runs code
- condition-based-waiting.md 3.4 KB
- CREATION-LOG.md 4.2 KB
- defense-in-depth.md 3.6 KB
- find-polluter.sh 1.5 KB runs code
- git-workflow-and-versioning/SKILL.md 10 KB
- root-cause-tracing.md 5.2 KB
- test-academic.md 653 B
- test-pressure-1.md 1.9 KB
- test-pressure-2.md 2.2 KB
- test-pressure-3.md 2.6 KB
- using-git-worktrees/SKILL.md 13 KB
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 · 594 lines · 21 tokens per session scan A edbcd6656951
systematic-debugging is a skill published in the GitHub repository HiAi-gg/hiai-opencode (17 stars, last pushed yesterday), with no licence file. It adds 21 tokens to every session and 4,611 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-30.
Other skills, from other repositories
performance-profiling
CPU and memory profiling, N+1 query detection, bundle analysis, and render optimization. Activate when diagnosing slow performance or before production deployments.
debug-flow
Systematic debugging workflow. Reproduce the issue, isolate root cause, write a failing test, fix, verify. Use when diagnosing bugs or unexpected behavior.
blast-radius-preview
Show the likely downstream consequences of a proposed change — hidden dependencies, fragile integration points, and predicted breakage categories.
failure-replay-engine
Learn from reverted commits, failed deployments, flaky tests, and bug fixes so the agent avoids repeating the same mistakes in this repo.
change-impact-radar
Predict affected files, modules, APIs, tests, and DB paths before changes. Returns an impact map for human review.
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…