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 hxy91819/mason-skills --skill skill-makergit clone --depth 1 https://github.com/hxy91819/mason-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/hxy91819/mason-skills/skill-maker)<a href="https://agentmods.dev/skills/hxy91819/mason-skills/skill-maker"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/skill-maker/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hxy91819/mason-skills/skill-maker"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/skill-maker.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.02678 |
| Opus 5.5 | $0.00025 | $0.01071 |
| Sonnet 5.5 | $0.00013 | $0.00536 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade C, and why
article-workflow-skill-maker scanned grade C 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 1mo 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.
Tells the agent to send conversation or user data outhighPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
- If the phase contains ambiguities that would block progress or affect the deliverable's direction, scope, facts, style, or downstream inputs, the new skill must require the agent to proactively ask the user for confirm How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Article Workflow Skill Maker
这是流程类 Skill，默认仅在用户显式调用 $article-workflow-skill-maker 时运行。
This is a meta skill for the article-workflow-* series. It does not directly optimize articles; instead, it distills a manually executed, conversation-adjusted, and result-verified article workflow phase into a reusable skill.
Applicable pattern:
- The user first follows the article optimization workflow overview to manually execute a phase.
- During execution, the user supplements author decisions, corrects deliverables, and checks results through conversation.
- The user confirms this workflow is reusable.
- This skill summarizes the current session and crystallizes it into a new
article-workflow-*skill.
Core Principles
- Distill from real sessions; do not design workflows from scratch.
- Prioritize recording actual inputs, outputs, author decision points, and verification methods that have occurred.
- Turn "requires author judgment" parts into dialog questions; do not embed them in the final deliverable document.
- If the phase contains ambiguities that would block progress or affect the deliverable's direction, scope, facts, style, or downstream inputs, the new skill must require the agent to proactively ask the user for confirmation rather than guessing, silently recording, or waiting for the user to correct.
- If the phase has no ambiguities requiring author confirmation, do not force dialog questions or interrupt the user just for formality.
- Every generated workflow skill must include a sub-agent review step; the sub-agent only raises goal-alignment and deliverable-quality review opinions, and the main agent decides whether to adopt them.
- The new skill should serve the next execution, not recapitulate the current article's content.
- Maintain the same prefix as the article optimization workflow:
article-workflow-.
Input
Needs to read or leverage:
- The article optimization workflow overview
- Phase goals, supplementary requirements, and correction feedback raised by the user in the current session
- Deliverables actually created or modified in the current session
- Existing workflow Skill names or files that the user wants used as style references; load named Skills through the host instead of assuming adjacent directories.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed d5a6a78f418a
- 1mo ago Changed · +2 lines 1f3c098c2155
- 1mo ago Changed · +7 lines 89276f00985b
- 1mo ago First seen · 281 lines · 63 tokens per session scan C 762cc9f670bc
article-workflow-skill-maker is a skill published in the GitHub repository hxy91819/mason-skills (3 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 2,678 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…