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 Webioinfo01/aweskill --skill aweskill-creatorgit clone --depth 1 https://github.com/Webioinfo01/aweskillWrote 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/webioinfo01/aweskill/aweskill-creator)<a href="https://agentmods.dev/skills/webioinfo01/aweskill/aweskill-creator"><img src="https://agentmods.dev/badge/skills/webioinfo01/aweskill/aweskill-creator/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/webioinfo01/aweskill/aweskill-creator"><img src="https://agentmods.dev/badge/skills/webioinfo01/aweskill/aweskill-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00106 | $0.00813 |
| Opus 5.5 | $0.00042 | $0.00325 |
| Sonnet 5.5 | $0.00021 | $0.00163 |
| Haiku 4.5 | $0.00011 | $0.00081 |
Grade A, and why
aweskill-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 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.
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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aweskill Creator
The creative loop is yours; the mechanics belong to the aweskill CLI. You interview, draft, test, and revise. The CLI guarantees valid scaffolding, frontmatter, and lifecycle. Read references/writing-guide.md before drafting skill prose.
The Loop
- Capture intent. If the current conversation already shows a workflow worth capturing, extract it from history first (tools used, step order, corrections, input/output formats). Confirm gaps with the user before drafting: what should the skill enable, when should it trigger, what output format, which examples pin the behavior down.
- Check for existing skills first. Run
aweskill find <query>andaweskill store list --verbose. Reuse, fork, or improve an existing skill before writing a new one. - Scaffold. Run
aweskill store create <name> --description "<trigger description>". The command validates the name, checks for conflicts, and writes a valid SKILL.md skeleton withreferences/. - Draft the body. Fill the skeleton following
references/writing-guide.md. Keep the body under ~500 lines; move detail intoreferences/files and link them from the body. - Project and test. Run
aweskill agent add skill <name> --global --agent <agent-id>, then try 2–3 realistic test prompts in fresh turns. Projections are symlinks: edits to the central-store copy go live immediately, so you can iterate without re-projecting. - Validate the mechanics. Run
aweskill doctor fix-skills --skill <name>(dry-run). Fix anything actionable before finishing. - Improve and repeat. Generalize feedback instead of layering rules, cut guidance that is not pulling its weight, rerun the test prompts. Stop when changes stop helping.
- Finish. Group it with
aweskill bundle add <bundle> <name>, or publish it: copy the skill directory into its own git repo so others canaweskill install owner/repo.
Where the Skill Lives
| Skill type | Create with |
|---|---|
| Personal, used across agents | aweskill store create <name> (central store) |
| Repo-specific, shared through git | aweskill store create <name> --dir <repo>/.agents/skills |
What ships with it
2 files 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 First seen · 41 lines · 106 tokens per session scan A 06005be86ad4
aweskill-creator is a skill published in the GitHub repository Webioinfo01/aweskill (35 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 106 tokens to every session and 813 once invoked, about $0.0004 per session on Opus 5.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-05.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.