Borrowing it
Nothing to install: this file belongs to AlphaLab-USTC/OhMyCode. 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/AlphaLab-USTC/OhMyCode/main/.agents/skills/add-feature/SKILL.mdgit clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCodeWrote 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/alphalab-ustc/ohmycode/add-feature)<a href="https://agentmods.dev/skills/alphalab-ustc/ohmycode/add-feature"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/add-feature/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/alphalab-ustc/ohmycode/add-feature"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/add-feature.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.00044 | $0.00937 |
| Opus 5.5 | $0.00018 | $0.00375 |
| Sonnet 5.5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
add-feature 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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a New Feature to OhMyCode
Add a major new capability that isn't covered by existing extension points (add-tool, add-provider).
Examples: hook system, MCP support, multi-session management, plugin architecture, new CLI commands, new compression strategy.
When to Use
- User wants a feature that requires new modules or modifying core modules
- User says "add hook support", "add MCP", "add plugin system", etc.
- The feature doesn't fit into the existing tool/provider/config pattern
IMPORTANT: Read First
Before doing anything, read docs/DEVELOPMENT_GUIDE.md — it contains:
- Project architecture and module dependency graph
- Code conventions (file size limits, naming, async patterns)
- Testing conventions
- Commit conventions
Step-by-Step Guide
Step 1: Understand the Request
Ask the user:
- What does the feature do?
- Who uses it? (end users via CLI? developers extending OhMyCode? both?)
- What existing modules does it interact with?
Step 2: Design the Architecture
Based on docs/DEVELOPMENT_GUIDE.md, determine:
-
Where does the code go?
- New module under
ohmycode/? (e.g.,ohmycode/hooks/) - Extends an existing module? (e.g., add to
ohmycode/core/) - Both?
- New module under
-
What interfaces does it expose?
- New Protocol/ABC?
- New config options?
- New CLI commands/flags?
- New slash commands in REPL?
-
What existing code needs to change?
- Check the dependency graph in DEVELOPMENT_GUIDE.md
- Minimize changes to existing modules
- Never introduce circular imports
-
Propose the design to the user before writing code.
Step 3: Implement with TDD
For each component:
- Write failing test in
tests/<module>/test_<component>.py - Run test to confirm it fails
- Implement the minimal code to pass
- Run ALL tests to ensure no regressions:
python3 -m pytest tests/ -v - Commit incrementally
Step 4: Integrate
If the feature requires changes to existing modules:
- Keep changes minimal and surgical
- Prefer adding new functions over modifying existing ones
- Use feature flags in config if the feature should be optional
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.
- 1mo ago First seen · 117 lines · 44 tokens per session scan A a695cd13ef83
add-feature is a skill published in the GitHub repository AlphaLab-USTC/OhMyCode (132 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 937 once invoked, about $0.0002 per session on Opus 5.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
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…