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 skills add wangyendt/wayne-skills --skill helpergit clone --depth 1 https://github.com/wangyendt/wayne-skillsWrote 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/wangyendt/wayne-skills/helper)<a href="https://agentmods.dev/skills/wangyendt/wayne-skills/helper"><img src="https://agentmods.dev/badge/skills/wangyendt/wayne-skills/helper.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.1 | $0.00051 | $0.01617 |
| Opus 5 | $0.00026 | $0.00809 |
| Sonnet 5 | $0.00010 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
pywayne-helper scanned grade A with 1 finding 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run(['python', 'worker.py']) How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pywayne Helper
项目配置管理辅助工具,实现跨进程、跨文件的参数共享机制。
Quick Start
from pywayne.helper import Helper
# 初始化(自动检测调用者所在目录作为项目根目录)
helper = Helper()
# 进程 A:写入配置
helper.set_module_value('database', 'host', value='127.0.0.1')
# 进程 B:读取配置(自动等待直到值存在)
db_host = helper.get_module_value('database', 'host', max_waiting_time=10)
print(f"数据库主机: {db_host}")
跨进程/跨文件参数共享
Helper 通过项目根目录下的 YAML 配置文件实现参数共享:
project_root/
├── common_info.yaml # 配置文件,自动创建
├── module_a/ # 模块 A
└── module_b/ # 模块 B
工作原理:
- 任何模块初始化 Helper 实例,自动定位到项目根目录
- 配置文件统一位于
{project_root}/common_info.yaml - 各模块通过
set_module_value写入配置 - 各模块通过
get_module_value读取配置 - 支持等待机制,确保读取到其他进程写入的值
适用场景:
| 场景 | 说明 |
|---|---|
| 多进程协作 | 进程 A 写配置,进程 B 读配置 |
| 分布式任务 | 主进程设置参数,子进程读取执行 |
| 配置传递 | 程序启动时写入配置,后续模块读取 |
| 动态参数 | 模块间共享动态生成的参数(如 token、临时 ID) |
Initialization
# 使用调用者所在目录作为项目根目录(推荐)
helper = Helper('./')
# 指定项目根目录
helper = Helper('/path/to/project')
# 自定义配置文件名
helper = Helper('/path/to/project', config_file_name='shared_config.yaml')
Methods
set_module_value
设置嵌套配置键的值。
# 写入数据库配置
helper.set_module_value('database', 'host', value='127.0.0.1')
helper.set_module_value('database', 'port', value=5432)
# 写入 API 配置
helper.set_module_value('api', 'token', value='abc123')
helper.set_module_value('api', 'endpoint', value='https://api.example.com')
# 写入共享临时参数
helper.set_module_value('shared', 'temp_id', value='temp_123')
helper.set_module_value('shared', 'status', value='running')
参数说明:
*keys: 按嵌套层级排列的键value: 要设置的值
get_module_value
获取嵌套配置键的值,支持等待机制。
# 基本获取
host = helper.get_module_value('database', 'host')
# 等待最多 10 秒,直到值存在(跨进程场景)
host = helper.get_module_value('database', 'host', max_waiting_time=10)
# 禁用调试输出
host = helper.get_module_value('database', 'host', debug=False)
# 未找到时返回 None
if host is None:
print("配置未找到")
参数说明:
*keys: 按嵌套层级排列的键max_waiting_time(可选): 最大等待时间(秒),轮询配置文件直到值存在debug(可选): 是否启用调试信息,默认 True
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.
- 8d ago First seen · 247 lines · 51 tokens per session scan A 6dda21185cdf
pywayne-helper is a skill published in the GitHub repository wangyendt/wayne-skills (8 stars, last pushed 12d ago), licensed MIT. It adds 51 tokens to every session and 1,617 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…