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/customize-response-stylenpx skills add AlphaLab-USTC/OhMyCode --skill customize-response-stylegit 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/customize-response-style)<a href="https://agentmods.dev/skills/alphalab-ustc/ohmycode/customize-response-style"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/customize-response-style.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.00036 | $0.01129 |
| Opus 5 | $0.00018 | $0.00564 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
customize-response-style 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customize OhMyCode's Response Style
Change how OhMyCode renders output in the terminal — colors, formatting, tool call display, token usage display.
When to Use
- User says "change the colors", "make output cleaner", "customize the theme"
- User wants to modify how tool calls, errors, or streaming text are displayed
- User wants to add/remove elements from the output (e.g., hide token counts)
Where Rendering Happens
All rendering logic is in ohmycode/cli.py → render_stream() function. It consumes events from the conversation loop and prints them using rich.console.Console.
Current rendering:
| Event | Current Style |
|---|---|
TextChunk |
Plain text, streamed character by character |
ToolCallStart |
▶ <tool_name> in cyan + params in dim |
ToolCallResult (success) |
✓ + green output (truncated to 500 chars) |
ToolCallResult (error) |
✗ + red error message |
TurnComplete |
Tokens: prompt=X completion=Y total=Z in dim |
How to Customize
Option 1: Edit render_stream() Directly
Open ohmycode/cli.py and find async def render_stream(). Modify the rich markup:
# Change tool call header color from cyan to blue
console.print(f"\n[blue]▶ {event.tool_name}[/blue]", highlight=False)
# Add a box around tool results
from rich.panel import Panel
console.print(Panel(output, title="Tool Result", border_style="green"))
# Hide token usage
# Comment out or delete the TurnComplete rendering block
Option 2: Add Rich Themes
Create a custom theme at the top of cli.py:
from rich.theme import Theme
ohmycode_theme = Theme({
"tool.name": "bold magenta",
"tool.success": "green",
"tool.error": "bold red",
"tool.params": "dim italic",
"status": "dim cyan",
"prompt": "bold yellow",
})
console = Console(theme=ohmycode_theme)
Then use style names in print calls:
console.print(f"▶ {event.tool_name}", style="tool.name")
Option 3: Add Markdown Rendering for AI Responses
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 · 133 lines · 36 tokens per session scan A 7462be1583d0
customize-response-style is a skill published in the GitHub repository AlphaLab-USTC/OhMyCode (131 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,129 once invoked, about $0.0002 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…