What is quantum-shield CLAUDE.md?

A set of project instructions for Quantum Shield, a system for storing assets using signatures designed to resist future quantum-computer attacks. It also describes the project's Rust backend, Next.js web interface, and blockchain contracts.

Use it when working on Quantum Shield code, including its backend, web interface, smart contracts, translations, API data, loading states, and accessibility.

It gives a coding agent the project's rules and structure so changes follow its security, language, data, accessibility, and blockchain requirements.

How kota1026/quantum-shield configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kota1026/quantum-shield. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/kota1026/quantum-shield/claude/research-emerging-tech-opportunities-dH6pR/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/kota1026/quantum-shield

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/kota1026/quantum-shield/claude-md/github.svg)](https://agentmods.dev/instructions/kota1026/quantum-shield/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/kota1026/quantum-shield/claude-md"><img src="https://agentmods.dev/badge/instructions/kota1026/quantum-shield/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/kota1026/quantum-shield/claude-md"><img src="https://agentmods.dev/badge/instructions/kota1026/quantum-shield/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 982 This file is loaded in full into every session.

When invoked 982 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00982	$0.00982
Opus 5.5	$0.00393	$0.00393
Sonnet 5.5	$0.00196	$0.00196
Haiku 4.5	$0.00098	$0.00098

Measured 2mo ago against content hash 011ce679bb58, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

quantum-shield 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 2mo 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.

CLAUDE.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quantum Shield

Post-quantum asset custody protocol: Dilithium + SPHINCS+ dual NIST signatures, Prover Pool, VRF, Time Lock.

Project Structure

src/api/api/          Rust/Axum backend (port 8080)
src/frontend/web/     Next.js frontend (port 3000)
src/contracts/        Solidity (L1 Sepolia + L3 Anvil)

Universal Rules

NO mock/fallback data in non-test files. MOCK_, FALLBACK_, DEMO_ patterns are blocked by hooks.
All text via t('key') - no hardcoded Japanese/English strings.
Types flow one direction: Backend types.rs -> Frontend types.ts. Frontend never defines its own API types.
snake_case from API, camelCase in frontend - use serde rename_all on backend, transform in API client layer.
L1 = Sepolia (chain 11155111). Never create a new L1. Use existing contracts in .claude/rules/blockchain.md.
L3 = local Anvil (chain 31337) for dev. L3 testnet = Arbitrum Sepolia (chain 421614) deployed 2026-03-03.
Loading/Error/Empty - every data-fetching component must handle all 3 states.
WCAG 2.1 AA - aria-labels, 44px tap targets, 4.5:1 contrast ratio.

Domain Rules

Detailed rules are in .claude/rules/:

frontend.md - React/Tailwind/i18n/a11y
backend.md - Rust/sqlx/API structure/DB
blockchain.md - L1/L3 addresses, chain config
integration.md - Type flow, API contract, FALLBACK removal
testing.md - E2E patterns, cargo test, stub detection

Quick Start

docker compose up -d postgres redis rabbitmq l3-node minio minio-init
cd src/api/api && DATABASE_URL="postgresql://quantum:quantum_dev@localhost:5432/quantum_shield" sqlx migrate run
cargo run --bin api-server                  # Backend on :8080
cd src/frontend/web && pnpm install && pnpm dev  # Frontend on :3000

Key File References

Category	Path
Backend config	`src/api/api/config/default.yaml`
Backend types	`src/api/api/src/types.rs`
Backend routes	`src/api/api/src/routes/`
Frontend types	`src/frontend/web/src/lib/api/*/types.ts`
Frontend hooks	`src/frontend/web/src/hooks/`
DB migrations	`src/api/api/migrations/`
L1 contracts	`src/contracts/l1/`
L3 contracts	`src/contracts/l3/`
Core sequences	`docs/core/SEQUENCES.md`
Actual state	`docs/ACTUAL_STATE.md`
Integration plan	`docs/INTEGRATION_METHODOLOGY_v2.md`

Read the full file on GitHub · 84 lines

Changes

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.

2mo ago First seen · 84 lines · 982 tokens per session scan A 011ce679bb58

Subscribe to this mod's changes

quantum-shield CLAUDE.md is an instructions file published in the GitHub repository kota1026/quantum-shield (0 stars, last pushed 2mo ago), licensed MIT. It adds 982 tokens to every session, about $0.0039 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-31.

blockchain cryptography defi ethereum nextjs post-quantum

quantum-shield CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
quantum-shield CLAUDE.mdkota1026/quantum-shield	Instructions file	0	2mo ago	MIT	A	982	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

quantum-shield: Instructions file for Claude Code