Borrowing it
Nothing to install: this file belongs to Katagiri-Hoshino-Lab/VibeCodeHPC. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Katagiri-Hoshino-Lab/VibeCodeHPC/main/CLAUDE.mdgit 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/instructions/katagiri-hoshino-lab/vibecodehpc/claude-md)<a href="https://agentmods.dev/instructions/katagiri-hoshino-lab/vibecodehpc/claude-md"><img src="https://agentmods.dev/badge/instructions/katagiri-hoshino-lab/vibecodehpc/claude-md/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/instructions/katagiri-hoshino-lab/vibecodehpc/claude-md"><img src="https://agentmods.dev/badge/instructions/katagiri-hoshino-lab/vibecodehpc/claude-md.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.01693 | $0.01693 |
| Opus 5 | $0.00847 | $0.00847 |
| Sonnet 5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
VibeCodeHPC CLAUDE.md 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeCodeHPC
Multi-CLI Multi-Agent Auto-Tuning Framework.
Project Overview
General-purpose multi-agent orchestration framework. HPC optimization is one workflow — pluggable strategies support any auto-tuning task.
Language Priority
Python → TypeScript (port) → Shell (minimal wrappers)
Design Principles
- No external orchestration framework (no CrewAI/AutoGen/LangGraph)
- Agent directory isolation without git worktree
- Use each CLI's native multi-agent capabilities directly
- No hardcoded paths — must run on WSL/macOS/Linux/supercomputers
- tmux-based IPC
- Unified TUI display
Package Structure
vibecodehpc/
├── adapters/ # CLI adapters (8 CLIs supported, see docs/cli_support_matrix.md)
│ └── base.py # CLIAdapter ABC
├── registry.py # AgentRegistry (JSONL-backed)
├── tmux_utils.py # tmux session/pane management
├── agent_manager.py # spawn/message/health
├── hooks/ # CLI-agnostic hook intents
└── monitor/ # periodic_monitor, periodic_enter
Component Classification
- Core: tmux communication, registry, hooks, ChangeLog+SOTA, budget, SSH/HPC integration
- Role: PM, SE, PG, CD (experimental), SOLO (alternative)
- Skill: Optimization templates, parallelization, sub-agent, report generation
- Workflow: Multi-agent auto-tuning, optimization cycle, evolutionary exploration
Reference Resources
../VibeCodeHPC-jp/— Original implementation (read-only)../3rd-party-repos/VibeCodeHPC_iWAPT/— Paper and figures../3rd-party-repos/openclaw/— Skills/extension referencedev/— Development docs (ARCHITECTURE, REQUIREMENTS, CLI_METADATA, TODO, etc.)
Available Tools
python3 -m vibecodehpc setup— create tmux sessions and agent panespython3 -m vibecodehpc send <agent> "msg"— inter-agent messagingpython3 -m vibecodehpc status/health— agent status checkvibecodehpc/monitor/periodic_monitor.py— background context/budget monitoringvibecodehpc/monitor/periodic_enter.py— auto-send Enter to prevent IPC message stallAgent-shared/skills/*/scripts/*.py— analytics tools (budget, SOTA, changelog, context)
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.
- 11d ago First seen · 141 lines · 1,693 tokens per session scan A 7b7005983234
VibeCodeHPC CLAUDE.md is an instructions file published in the GitHub repository Katagiri-Hoshino-Lab/VibeCodeHPC (39 stars, last pushed 5mo ago), licensed MIT. It adds 1,693 tokens to every session, about $0.0085 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.