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/matrixages/polywise/skill-generatornpx skills add MatrixAges/polywise --skill skill-generatorgit clone --depth 1 https://github.com/MatrixAges/polywiseWrote 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/matrixages/polywise/skill-generator)<a href="https://agentmods.dev/skills/matrixages/polywise/skill-generator"><img src="https://agentmods.dev/badge/skills/matrixages/polywise/skill-generator.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.00029 | $0.00285 |
| Opus 5 | $0.00015 | $0.00143 |
| Sonnet 5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
skill-generator 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 today.
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 Generator
This skill is used to extend new specialized skills for AI in the project, ensuring new skill files meet the project's format requirements.
1. Skill Structure
Each new skill must be placed in the .opencode/skills/{skill-name}/ directory, and its main file must be named SKILL.md.
2. SKILL.md Format Requirements
YAML Frontmatter description must be included at the top of the file, containing the following two fields:
---
name: { skill-name }
description: { A piece of English or Chinese text describing when and what the skill does }
---
3. Generation Guide
- Create Directory: Create a new skill-named folder under
.opencode/skills/. - Write Content: Use Markdown syntax to detail the following under the skill:
- Core architecture/principles
- Naming and code style specifications
- Specific execution best practices
- Mandatory red lines (what absolutely cannot be done)
- Language Alignment: New skill content should尽量 use Chinese (to align with unified specifications), but the YAML header
namemust be English letters and hyphens.
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.
- today First seen · 34 lines · 29 tokens per session scan A 6fd475c9ba34
skill-generator is a skill published in the GitHub repository MatrixAges/polywise (659 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 285 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
explain-for
Explain a topic, a piece of code, an error, or a design decision calibrated to one named audience — a 5-year-old, a 5th grader, a manager, a designer, a graduate student, a parent. Resolves who the explanation is for (from the request, or from what memory already records about that person), establishes the ground…
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.