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/devswha/oh-my-gajae-code/example-skillnpx skills add devswha/oh-my-gajae-code --skill example-skillgit clone --depth 1 https://github.com/devswha/oh-my-gajae-codeWhat 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.00050 | $0.00305 |
| Opus 5 | $0.00025 | $0.00152 |
| Sonnet 5 | $0.00010 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
example-skill 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 2d 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.
What it actually says
Example Skill
This is a template skill. It exists to show the on-disk shape of a skill that ships inside an oh-my-gajae-code plugin. Delete it (or rewrite it) before publishing a real plugin.
What a real skill should contain
- A precise
descriptionin the frontmatter above — the model uses it to decide when to activate the skill, so describe the trigger conditions, not just the topic. - Concrete, ordered instructions the agent should follow when the skill is active.
- Explicit boundaries: what the skill must NOT do.
Structure recap
plugins/<plugin-name>/
├── .claude-plugin/
│ └── plugin.json # plugin manifest
├── commands/ # slash commands → /<plugin-name>:<file>
│ └── changelog.md
└── skills/ # skills, one directory per skill
└── example-skill/
└── SKILL.md # this file
When this plugin is installed, this skill becomes available to the gjc agent and
the /example-plugin:changelog slash command appears in the command palette.
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.
- 2d ago First seen · 35 lines · 50 tokens per session scan A 0e695c0985c7
example-skill is a skill published in the GitHub repository devswha/oh-my-gajae-code (34 stars, last pushed 14d ago), licensed MIT. It adds 50 tokens to every session and 305 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-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…