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 instructions/kota1026/quantum-shield/claude-mdgit 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/instructions/kota1026/quantum-shield/claude-md)<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="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.00982 | $0.00982 |
| Opus 5 | $0.00491 | $0.00491 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
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 5d 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 — 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-> Frontendtypes.ts. Frontend never defines its own API types. - snake_case from API, camelCase in frontend - use serde
rename_allon 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/a11ybackend.md- Rust/sqlx/API structure/DBblockchain.md- L1/L3 addresses, chain configintegration.md- Type flow, API contract, FALLBACK removaltesting.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 |
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.
- 5d ago First seen · 84 lines · 982 tokens per session scan A 011ce679bb58
quantum-shield CLAUDE.md is an instructions file published in the GitHub repository kota1026/quantum-shield (0 stars, last pushed 8d ago), licensed MIT. It adds 982 tokens to every session, about $0.0049 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-31.
Other instructions, from other repositories
WAIaaS CLAUDE.md
Instructions for waiaas/WAIaaS, covering waiaas project rules, language, communication, schema & type system and database.
ponscli CLAUDE.md
Claude Code instructions for mesutgulecen/ponscli, covering ponscli, the rule that matters most, layout, verifying a change and things that will bite.
ponscli AGENTS.md
AGENTS.md instructions for mesutgulecen/ponscli, a project described as: Unofficial command-line interface for the Pons launchpad on Robinhood Chain.
lineth-monorepo AGENTS.md
AGENTS.md instructions for LFDT-Lineth/lineth-monorepo, covering agents.md, documentation precedence, agent entry points, local agent workflows and discoverability index.
suwappubot CLAUDE.md
Claude Code instructions for 0xSoftBoi/suwappubot, covering claude.md, workflow, response length, git conventions and git operations.
behavioral-prediction-mcp CLAUDE.md
Instructions for ChainAware/behavioral-prediction-mcp, covering chainaware behavioral prediction mcp, project overview, mcp tools (14 total), batch pipeline and repository structure.