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/tkellogg/open-strix/skill-creatornpx skills add tkellogg/open-strix --skill skill-creatorgit clone --depth 1 https://github.com/tkellogg/open-strixWrote 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/tkellogg/open-strix/skill-creator)<a href="https://agentmods.dev/skills/tkellogg/open-strix/skill-creator"><img src="https://agentmods.dev/badge/skills/tkellogg/open-strix/skill-creator.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.00058 | $0.00330 |
| Opus 5 | $0.00029 | $0.00165 |
| Sonnet 5 | $0.00012 | $0.00066 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
skill-creator 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.
What it actually says
skill-creator
Create or update local skills in this agent home repo.
Where Skills Go
User-editable skills belong in:
skills/<skill-name>/SKILL.md
Example:
skills/triage-issues/SKILL.md
Built-in skills are exposed at:
/.open_strix_builtin_skills/<skill-name>/SKILL.md
Treat built-in skills as read-only.
Critical Rule: Trigger Description
The YAML frontmatter description is the trigger signal. It must make it obvious
when the skill should be used.
Every skill description should include:
- what the skill does
- exact "when to use" triggers
- what it should not be used for
Bad description:
Helps with docs.
Good description:
Create and update release notes from git history. Use when the user asks for changelogs, release summaries, or version notes. Do not use for code changes.
Authoring Checklist
- Write frontmatter with
nameand a high-signaldescription. - Add concise execution steps in the SKILL body.
- Include concrete paths/commands the agent should run.
- Keep scope narrow; split broad domains into multiple skills.
- Prefer deterministic instructions over generic advice.
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 · 46 lines · 58 tokens per session scan A 0cd62f136445
skill-creator is a skill published in the GitHub repository tkellogg/open-strix (84 stars, last pushed 29d ago), licensed MIT. It adds 58 tokens to every session and 330 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…