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/appleweiping/weiping_lab/claude-mdgit clone --depth 1 https://github.com/appleweiping/WEIPING_LABWrote 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/appleweiping/weiping_lab/claude-md)<a href="https://agentmods.dev/instructions/appleweiping/weiping_lab/claude-md"><img src="https://agentmods.dev/badge/instructions/appleweiping/weiping_lab/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 | $0.01558 | $0.01558 |
| Opus 5 | $0.00779 | $0.00779 |
| Sonnet 5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
WEIPING_LAB 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 4d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - WEIPING_LAB
Weiping Lab is an autonomous research workbench. Treat it as software that assists research, not as an authority that can invent evidence.
Session Start
- Run agentmemory recall for the current task when past context matters.
- Read the smallest relevant project files for current truth:
AGENTS.md,README.md,pyproject.toml,lab/runtime.py,lab/core/config.py, and the files you will edit. - Run
git status --short --branch. - For non-trivial work, follow
.codex/skills/weiping-lab/SKILL.md. An external shared resource may be consulted only through an explicitly configuredAGENT_RESOURCE_ROOT; it is never required for startup, verification, or release.
Do not depend on retired mailbox or old markdown session systems. Stable public-safe knowledge belongs in project docs or the maintained wiki; local runtime observations belong in active agentmemory or the workspace outbox.
Identity
- Name:
vlab - Role: phenomenon-driven research discovery, kill-first ideation, experiment planning, evidence-gated paper writing, and audit support
- Runtime memory: active agentmemory via
AGENTMEMORY_URL - Local fallback: redacted
agentmemory-outbox.jsonlunder the configured workspace memory directory - Workspace:
WEIPING_LAB_WORKSPACE_ROOTor./workspace; legacyVIPIN_LAB_WORKSPACE_ROOTremains a fallback
Never store API keys, bearer tokens, account secrets, raw private logs, or private documents in memory or tracked source.
Quick Start
cd WEIPING_LAB
python -m pip install -e ".[dev]"
copy .env.example .env
vlab status --json
uvicorn api.server:app --reload --port 8001
npm --prefix ui run dev
Common commands:
vlab discover "LLM4Rec"
vlab extend "LLM4Rec" --method "..." --results "..." --limits "..."
vlab transfer "conformal prediction" "LLM4Rec"
vlab pipeline <idea_id>
vlab resume <idea_id>
vlab ideas
vlab sessions
vlab show <session_id>
python scripts/release_scan.py
Architecture
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.
- 4d ago First seen · 170 lines · 1,558 tokens per session scan A 3f4415c28dc8
WEIPING_LAB CLAUDE.md is an instructions file published in the GitHub repository appleweiping/WEIPING_LAB (120 stars, last pushed 7d ago), licensed MIT. It adds 1,558 tokens to every session, about $0.0078 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
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.