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 commands/kota1026/quantum-shield/phase6-startgit clone --depth 1 https://github.com/kota1026/quantum-shieldWrote 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/commands/kota1026/quantum-shield/phase6-start)<a href="https://agentmods.dev/commands/kota1026/quantum-shield/phase6-start"><img src="https://agentmods.dev/badge/commands/kota1026/quantum-shield/phase6-start.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 | $0.00000 | $0.00724 |
| Opus 5 | $0.00000 | $0.00362 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
phase6-start 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 3d 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
Phase 6 $ARGUMENTS 開始
今すぐ以下を実行してください(指示ではなく、実際に実行):
STEP 1: 進捗状況を確認
docs_new/01_phase/06_phase6/PHASE6_PROGRESS.md を読み込み、$ARGUMENTS システムの進捗状況を確認してください。
STEP 2: 未完了画面を特定
PHASE6_PROGRESS.md から以下を分析:
- Status が「Pending」または「In Progress」の画面を特定
- 未完了画面の中で最初の画面番号を確認
- その画面名と必要な実装項目(UI, A11y, E2E, Persona Test, PIR)を把握
STEP 3: 必須ファイルを読み込む
以下のファイルを今すぐ並列で読み込んでください:
docs_new/01_phase/04_phase4/01_design/assets/design-concept-5-japan-premium.htmlapps/web/tailwind.config.tsapps/web/src/styles/globals.cssdocs_new/02_agents_prompt/02_prompts/30_ui_impl.md
STEP 4: インフラ確認
apps/web/postcss.config.js が存在するか確認し、無ければ作成。
STEP 5: 対象モック確認
docs_new/01_phase/04_phase4/01_design/system_*$ARGUMENTS*/wip/mocks/ から、STEP 2 で特定した未完了画面に対応するHTMLファイルを確認。
STEP 6: 初期化完了報告
以下の形式で報告を出力:
## Phase 6 初期化完了
### 進捗確認結果
- PHASE6_PROGRESS.md: ✅ 読み込み完了
- 対象システム: $ARGUMENTS
- 完了済み画面数: {completed}
- 未完了画面数: {pending}
### 次に実装する画面
- 画面番号: {screen_number}
- 画面名: {screen_name}
- 未完了項目: {UI/A11y/E2E/Persona Test/PIR}
### 読み込んだファイル
- design-concept-5-japan-premium.html: ✅
- tailwind.config.ts: ✅
- globals.css: ✅
- 30_ui_impl.md: ✅
### インフラ検証
- postcss.config.js: ✅ 存在
STEP 7: 未完了画面の実装開始
初期化完了報告を出力後、STEP 2 で特定した未完了画面のUI実装を開始してください。
重要:
- このコマンドを受けたら、上記を説明せずに実行してください。
- 必ず PHASE6_PROGRESS.md を確認し、未完了の画面から順番に実装を進めてください。
- 既に完了している画面は飛ばし、効率的に進めてください。
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.
- 3d ago First seen · 71 lines · 0 tokens per session scan A 2d61ec89e516
phase6-start is a command published in the GitHub repository kota1026/quantum-shield (0 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 724 tokens. 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 commands, from other repositories
audit
Full security audit of a Solidity/Vyper/Rust contract or directory. Runs the entire vuln-skills library and dispatches DeFi specialist subagents based on detected protocol type.
audit-deps
Audit third-party dependencies — resolve installed versions, cross-reference known-vulnerable releases, and flag vendored code that has diverged from upstream.
pre-deploy
Interactive pre-launch security checklist — walk the operational and code-safety gates and produce a final GO / NO-GO with each item PASS / FAIL / N-A.
audit-live
Audit a deployed contract on a live chain. Pulls verified source from the block explorer, optionally forks the chain for live-state simulation.
audit-multi-chain
Diff the on-chain configuration of one contract deployed across multiple chains — owner, oracle, fees, timelock, pause state, proxy impl — and flag the chain that drifted.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.