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/rakaarwaky/qwen-web-arwaky/create-utility-pythonnpx skills add rakaarwaky/qwen-web-arwaky --skill create-utility-pythongit clone --depth 1 https://github.com/rakaarwaky/qwen-web-arwakyWrote 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/rakaarwaky/qwen-web-arwaky/create-utility-python)<a href="https://agentmods.dev/skills/rakaarwaky/qwen-web-arwaky/create-utility-python"><img src="https://agentmods.dev/badge/skills/rakaarwaky/qwen-web-arwaky/create-utility-python.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.00040 | $0.00699 |
| Opus 5 | $0.00020 | $0.00349 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
create-utility-python 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-utility-python
Utility = stateless standalone functions. No class, no self, no domain rules. File: utility_<domain>_<role>.py.
Allowed imports: Taxonomy only. Forbidden: Capabilities, Agent, Surface, Contract.
Role Naming
Utility role suffixes are unlimited. The role name is chosen based on demand and must describe the technical responsibility and concern of the file.
Templates
"""<Domain> utility functions — stateless, pure, domain-agnostic.
Module-level functions only — no classes, no state.
"""
# from shared.user.taxonomy_user_vo import UserVO # uncomment if using VOs
def <function_name>(<param_name>: str) -> str:
"""<Description of what this function does>.
Args:
<param_name>: <description>
Returns:
<description of return value>
"""
# pure function logic here
pass
def <function_name>(<param_name>: str) -> str:
"""<Description of what this function does>.
Args:
<param_name>: <description>
Returns:
<description of return value>
"""
# pure function logic here
pass
Rules
- Only module-level functions — no
class, noself. - Pure + deterministic — no
random, nodatetime.now(), no global mutable state. - Domain-agnostic — no business rules, no layer-name knowledge.
- Reusable — used by ≥2 modules; if single consumer → keep as private helper.
- I/O allowed only if all above hold.
Keep as private helper if ANY: uses self, domain-specific, single consumer.
Extract here only if ALL: no self, pure/I/O-safe, domain-agnostic, ≥2 consumers.
Workflow
- Confirm ≥2 consumers, stateless, domain-agnostic.
- Create
utility_<domain>_<role>.py. - Register in
__init__.py. python -c "import <module>".
Checklist
- Only module-level functions — no class.
- No
self, no instance state. - Pure/deterministic (or I/O justified: domain-agnostic + reusable).
- No business rules or layer-name knowledge.
- Used by ≥2 modules.
- No import from Capabilities, Agent, Surface, Contract.
- No magic constants (→
taxonomy_*_constant.py). -
python -c "import <module>"passes.
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 · 96 lines · 40 tokens per session scan A 92b320414ad2
create-utility-python is a skill published in the GitHub repository rakaarwaky/qwen-web-arwaky (11 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 699 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…