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/alphalab-ustc/ohmycode/add-toolnpx skills add AlphaLab-USTC/OhMyCode --skill add-toolgit clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCodeWhat 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.00024 | $0.00788 |
| Opus 5 | $0.00012 | $0.00394 |
| Sonnet 5 | $0.00005 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
add-tool 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a New Tool to OhMyCode
Create a new tool that the AI assistant can use during conversations.
When to Use
- User says "add a tool", "create a tool", "I want a new tool"
- User describes a capability they want the AI to have (e.g., "I want it to run SQL queries")
Prerequisites
- Read
docs/DEVELOPMENT_GUIDE.mdfor project conventions - Read
ohmycode/tools/base.pyto understandTool,ToolContext,ToolResult,@register_tool - Look at an existing tool (e.g.,
ohmycode/tools/bash.py) as reference
Step-by-Step Guide
Step 1: Define the Tool
Ask the user:
- Tool name — short, lowercase, snake_case (e.g.,
sql_query,docker_run) - Description — one sentence for the LLM to understand when to use it
- Parameters — what inputs does it need? (JSON Schema format)
- Concurrent safety — can it run in parallel with other tools? (True for read-only, False for side effects)
Step 2: Create the Tool File
Copy the template from templates/tool_template.py to ohmycode/tools/<tool_name>.py.
Fill in:
name,description,parameters,concurrent_safeclass attributesexecute()method with the actual logic
Step 3: Write Tests (TDD)
Create tests/tools/test_<tool_name>.py:
import pytest
from ohmycode.tools.base import ToolContext
from ohmycode.tools.<tool_name> import <ToolClass>
@pytest.fixture
def ctx(tmp_path):
return ToolContext(mode="auto", agent_depth=0, cwd=str(tmp_path), is_sub_agent=False)
@pytest.mark.asyncio
async def test_<tool_name>_basic(ctx):
tool = <ToolClass>()
result = await tool.execute({"param": "value"}, ctx)
assert not result.is_error
assert "expected" in result.output
Step 4: Verify
python3 -m pytest tests/tools/test_<tool_name>.py -v # New tests pass
python3 -m pytest tests/ -v # No regressions
Step 5: Test End-to-End
ohmycode -p "Use the <tool_name> tool to ..." --mode auto
Step 6: Commit
What ships with it
1 file 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.
- 3d ago First seen · 96 lines · 24 tokens per session scan A e7313d6cdcb8
add-tool is a skill published in the GitHub repository AlphaLab-USTC/OhMyCode (131 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 788 once invoked, about $0.0001 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 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…