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/yxhpy/openuser/claude-mdgit clone --depth 1 https://github.com/yxhpy/openuserWhat 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.02127 | $0.02127 |
| Opus 5 | $0.01064 | $0.01064 |
| Sonnet 5 | $0.00425 | $0.00425 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
openuser 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 2d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with the OpenUser project.
Project Overview
OpenUser is an intelligent digital human system that enables users to create personalized AI avatars with their own voice, images, and videos. The system features hot-reloadable plugins, skills, scheduled tasks, and multi-platform integrations.
Core Components:
- Digital Human Engine - Custom solution integrating Wav2Lip, GFPGAN, SadTalker
- Plugin System - Hot-reloadable plugins with auto-installation
- Agent System - Self-updating AI agents with parameterized environments
- Integration Layer - Feishu, WeChat Work, Web interface
- Scheduler - Cron-based task automation
Tech Stack: Python 3.10+, FastAPI, SQLAlchemy, Redis, Celery
Core Principles
1. Hot Reload Everything
- Plugins can be installed/updated without restart
- Skills can be modified on-the-fly
- System prompts are dynamically reloadable
- Configuration changes apply immediately
2. Agent Self-Evolution
- Agents can update themselves via prompts
- Auto-install required plugins
- Create custom plugins programmatically
- All environments are parameterized
3. Maximum Extensibility
- Plugin-based architecture
- Event-driven design
- API-first approach
- Modular components
4. Documentation-Driven Development
- All features documented in
docs/modules/REGISTRY.md - API docs auto-generated from code
- Known issues tracked in
docs/troubleshooting/ - Check registry before implementing new features
5. Test-Driven Development
- 100% test coverage required
- Tests run automatically after code changes
- Integration tests for all plugins
- E2E tests for critical workflows
Architecture
Directory Structure
openuser/
├── .claude/ # Claude Code extensions
│ ├── skills/ # Project-specific skills
│ ├── hooks/ # Event hooks
│ ├── agents/ # AI agents
│ └── scripts/ # Helper scripts
├── src/
│ ├── core/ # Core system
│ │ ├── plugin_manager.py # Plugin hot-reload
│ │ ├── agent_manager.py # Agent lifecycle
│ │ └── config_manager.py # Dynamic config
│ ├── plugins/ # Plugin implementations
│ ├── agents/ # Agent definitions
│ ├── api/ # FastAPI endpoints
│ ├── integrations/ # Platform integrations
│ │ ├── feishu/
│ │ └── wechat/
│ ├── models/ # Digital human models
│ └── utils/ # Utilities
├── tests/ # Test suites
├── docs/ # Documentation
└── scripts/ # Deployment scripts
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.
- 2d ago First seen · 307 lines · 2,127 tokens per session scan A a091960babfd
openuser CLAUDE.md is an instructions file published in the GitHub repository yxhpy/openuser (2 stars, last pushed 7mo ago), licensed MIT. It adds 2,127 tokens to every session, about $0.0106 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
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.