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 skills/yellowbee686/everything-analysis-agent/cbeta-researchnpx skills add yellowbee686/everything-analysis-agent --skill cbeta-researchgit clone --depth 1 https://github.com/yellowbee686/everything-analysis-agentWrote 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/yellowbee686/everything-analysis-agent/cbeta-research)<a href="https://agentmods.dev/skills/yellowbee686/everything-analysis-agent/cbeta-research"><img src="https://agentmods.dev/badge/skills/yellowbee686/everything-analysis-agent/cbeta-research.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.00067 | $0.00740 |
| Opus 5 | $0.00034 | $0.00370 |
| Sonnet 5 | $0.00013 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
cbeta-research 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CBETA Research
Overview
Use the mcp_servers/CbetaMCP submodule as the live tool server. This skill provides startup policy, tool selection, and citation workflows; it does not duplicate the MCP tool implementations.
Startup Policy
Do not start the MCP server when the skill is loaded. Start it only when the user task needs a live CBETA query.
- Check the endpoint first:
python3 skills/cbeta-research/scripts/check_server.py --url http://localhost:18765/mcp/
- If unavailable, start on demand:
skills/cbeta-research/scripts/start_server.sh
When running inside an agent shell that cleans up background processes, keep the server in a long-running foreground session:
CBETA_MCP_FOREGROUND=1 skills/cbeta-research/scripts/start_server.sh
- Re-run the check. If it still fails, report dependency, port, or server-log diagnostics.
The default MCP endpoint is http://localhost:18765/mcp/.
Windows Preference
On Windows, prefer running CBETA MCP commands inside WSL2. Fall back to PowerShell only when WSL2 is unavailable or the user explicitly asks for native Windows execution.
- If the agent is already running in WSL2, use the normal Linux commands above.
- If the agent is running in native Windows PowerShell or CMD and WSL2 is available, run Linux commands through
wsl.exe -- bash -lc. - If WSL2 is unavailable, use
scripts\start_server.ps1from PowerShell. - Convert Windows paths such as
C:\Users\name\repoto WSL paths such as/mnt/c/Users/name/repobefore calling Linux scripts.
Example from native Windows:
wsl.exe -- bash -lc 'cd /mnt/c/path/to/everything-analysis-agent && skills/cbeta-research/scripts/start_server.sh'
Fallback from native PowerShell:
.\skills\cbeta-research\scripts\start_server.ps1
Query Workflow
- Use
references/tool-map.mdto choose the smallest useful tool set. - For broad discovery, start with
cbeta_all_in_oneorcbeta_search_sc. - For exact Buddhist canon metadata, use catalog or work tools before content retrieval.
- For final answers, prefer source-backed snippets from
get_cbeta_lines,cbeta_kwic_search, orget_juan_html. - Include
work,title,juan, andlineheadwhen available. Preserve traditional Chinese source text unless the user asks for simplified Chinese.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 77 lines · 67 tokens per session scan A 5711066916a8
cbeta-research is a skill published in the GitHub repository yellowbee686/everything-analysis-agent (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 740 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…