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 Katagiri-Hoshino-Lab/VibeCodeHPC --skill compile-warning-handlergit clone --depth 1 https://github.com/Katagiri-Hoshino-Lab/VibeCodeHPCWrote 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/katagiri-hoshino-lab/vibecodehpc/compile-warning-handler)<a href="https://agentmods.dev/skills/katagiri-hoshino-lab/vibecodehpc/compile-warning-handler"><img src="https://agentmods.dev/badge/skills/katagiri-hoshino-lab/vibecodehpc/compile-warning-handler/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/katagiri-hoshino-lab/vibecodehpc/compile-warning-handler"><img src="https://agentmods.dev/badge/skills/katagiri-hoshino-lab/vibecodehpc/compile-warning-handler.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.00026 | $0.00157 |
| Opus 5.5 | $0.00010 | $0.00063 |
| Sonnet 5.5 | $0.00005 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
compile-warning-handler 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 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.
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
Compile Warning Handler
Decision Matrix
Block job execution
- Parallelization disabled warnings
- Data race potential
- Memory access pattern issues
- Directive ignored warnings
Safe to proceed
- Optimization suggestions
- Deprecated feature warnings
- Performance improvement hints
Workflow
- Save output:
make 2>&1 | tee compile_vX.Y.Z.log - Classify warnings (block vs safe)
- Record in ChangeLog.md
compile.status: warning,compile.message: "..." - Proceed or fix based on classification
- If uncertain, consult SE
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 · 27 lines · 26 tokens per session scan A 0a9ec2d06e3a
compile-warning-handler is a skill published in the GitHub repository Katagiri-Hoshino-Lab/VibeCodeHPC (43 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 157 once invoked, about $0.0001 per session on Opus 5.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
trace
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode.
clio-kit-scientific-debugging
Use when this workflow is requested: Diagnoses stalled or cross-system failures and wrong, NaN, nondeterministic, or unexpectedly slow scientific results through falsifiable hypotheses across distinct fault classes, with evidence-cited verdicts before any fix. Not for designing benchmarks or pre-registered…
job-diagnose
Use when investigating I/O bottlenecks using a genuine Darshan profile and application logs. Triggers on "Darshan log", "why was this job slow", "I/O bottleneck". Not for metric interpretation alone; use io-performance.
mxl-troubleshoot
This skill should be used when MaxwellLink simulations stall, diverge, or produce missing/incorrect observables; it provides a first-aid checklist for sockets, units, and driver configuration.
ai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode.
peer-review
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…