Borrowing it
Nothing to install: this file belongs to yxhpy/openuser. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yxhpy/openuser/main/.claude/skills/auto-doc/SKILL.mdgit clone --depth 1 https://github.com/yxhpy/openuserWrote 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/skills/yxhpy/openuser/auto-doc)<a href="https://agentmods.dev/skills/yxhpy/openuser/auto-doc"><img src="https://agentmods.dev/badge/skills/yxhpy/openuser/auto-doc/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.
<a href="https://agentmods.dev/skills/yxhpy/openuser/auto-doc"><img src="https://agentmods.dev/badge/skills/yxhpy/openuser/auto-doc.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01693 |
| Opus 5.5 | $0.00012 | $0.00677 |
| Sonnet 5.5 | $0.00006 | $0.00339 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade B, and why
auto-doc scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
response = requests.post( "http://localhost:8000/api/v1/digital-human/create", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.post( How it starts
The opening of the file, as written. The whole thing — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Documentation Skill
This skill automatically updates documentation and module registry after code changes.
Trigger Conditions
This skill is triggered when:
- New feature is implemented
- API endpoints are added/modified
- Module structure changes
- Tests pass successfully
- User explicitly requests documentation update
Behavior
When triggered, this skill will:
- Detect Changes - Identify what was modified
- Update Module Registry - Add new modules to
docs/modules/REGISTRY.md - Update API Docs - Regenerate API documentation
- Update Integration Docs - Update integration guides if needed
- Update CHANGELOG - Record changes in CHANGELOG.md
- Verify Links - Check all documentation links are valid
- Record in Memory - Update project memory with changes
Documentation Structure
docs/
├── INDEX.md # Main documentation index
├── modules/
│ └── REGISTRY.md # Module registry (prevent duplication)
├── api/
│ ├── INDEX.md # API overview
│ ├── digital-human.md # Digital human endpoints
│ ├── plugins.md # Plugin endpoints
│ ├── agents.md # Agent endpoints
│ └── scheduler.md # Scheduler endpoints
├── integrations/
│ ├── FEISHU.md # Feishu integration guide
│ ├── WECHAT.md # WeChat Work integration guide
│ └── WEB.md # Web interface guide
└── troubleshooting/
├── KNOWN_ISSUES.md # Known issues and solutions
└── FAQ.md # Frequently asked questions
Module Registry Format
docs/modules/REGISTRY.md tracks all implemented modules to prevent duplication:
# Module Registry
## Core Modules
### Plugin Manager
- **Path**: `src/core/plugin_manager.py`
- **Purpose**: Hot-reload plugin system
- **Status**: ✅ Implemented
- **Test Coverage**: 100%
- **Dependencies**: None
- **API**: `PluginManager.load_plugin()`, `PluginManager.reload_plugin()`
### Agent Manager
- **Path**: `src/core/agent_manager.py`
- **Purpose**: AI agent lifecycle management
- **Status**: ✅ Implemented
- **Test Coverage**: 100%
- **Dependencies**: Plugin Manager
- **API**: `AgentManager.create_agent()`, `AgentManager.update_agent()`
## Plugins
### Image Processor
- **Path**: `src/plugins/image_processor.py`
- **Purpose**: Image preprocessing and enhancement
- **Status**: ✅ Implemented
- **Test Coverage**: 100%
- **Dependencies**: PIL, OpenCV
- **API**: `ImageProcessor.process()`
## Integrations
### Feishu Integration
- **Path**: `src/integrations/feishu/`
- **Purpose**: Feishu bot integration
- **Status**: 🚧 In Progress
- **Test Coverage**: 80%
- **Dependencies**: httpx
- **API**: `FeishuBot.send_message()`, `FeishuBot.handle_webhook()`
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 · 296 lines · 31 tokens per session scan B 0860c899ac2c
auto-doc is a skill published in the GitHub repository yxhpy/openuser (2 stars, last pushed 8mo ago), licensed MIT. It adds 31 tokens to every session and 1,693 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…