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 lofcz/LLMTornado --skill skill-creatorgit clone --depth 1 https://github.com/lofcz/LLMTornadoWrote 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/lofcz/llmtornado/skill-creator)<a href="https://agentmods.dev/skills/lofcz/llmtornado/skill-creator"><img src="https://agentmods.dev/badge/skills/lofcz/llmtornado/skill-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/lofcz/llmtornado/skill-creator"><img src="https://agentmods.dev/badge/skills/lofcz/llmtornado/skill-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 120 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 197 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 139 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 142 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00022 | $0.01543 |
| Opus 5 | $0.00011 | $0.00772 |
| Sonnet 5 | $0.00004 | $0.00309 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
skill-creator 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST \ How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creation and GitHub Workflow
Copy this checklist and track your progress:
Skill Creation Progress:
- [ ] Step 1: Gather skill requirements and specifications
- [ ] Step 2: Generate skill structure and SKILL.md
- [ ] Step 3: Create supporting scripts and files
- [ ] Step 4: Validate skill completeness
- [ ] Step 5: Prepare GitHub repository structure
- [ ] Step 6: Create and push Git branch
- [ ] Step 7: Generate pull request
- [ ] Step 8: Download to local disk
- [ ] Step 9: Verify local download
Step 1: Gather skill requirements and specifications
Collect the following information from the user:
- Skill name: Kebab-case name (e.g., "data-analyzer")
- Description: Brief one-line description
- Primary functionality: What the skill does
- Workflow steps: Sequential steps for execution
- Required tools: Any external tools or dependencies
- Trigger words: Keywords that activate this skill
- Expected inputs: What the user provides
- Expected outputs: What the skill produces
Step 2: Generate skill structure and SKILL.md
Create the main SKILL.md file with this structure:
---
name: [skill-name]
description: [Brief description of what this skill does]
---
## [Skill Title]
Copy this checklist and track your progress:
[Skill Name] Progress:
- Step 1: [First step]
- Step 2: [Second step]
- Step 3: [Third step] ...
## **Step 1: [First Step Name]**
[Detailed instructions for first step]
## **Step 2: [Second Step Name]**
[Detailed instructions for second step]
[Continue for all steps...]
Step 3: Create supporting scripts and files
If the skill requires automation, create:
- Python scripts: For complex logic or API interactions
- Bash scripts: For system operations and Git workflows
- Config files: For settings and parameters
- README.md: Usage instructions and examples
Step 4: Validate skill completeness
Check that the skill includes:
- Clear, sequential workflow steps
- Specific, actionable instructions
- Progress tracking checklist
- All necessary files
- Proper markdown formatting
- Front matter with name and description
What ships with it
8 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.
- 10d ago First seen · 225 lines · 22 tokens per session scan A f1a88b703a7c
skill-creator is a skill published in the GitHub repository lofcz/LLMTornado (639 stars, last pushed 23d ago), licensed MIT. It adds 22 tokens to every session and 1,543 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
author-pragma-dsl
Create and update validated pragma/v5 Expert, ExpertTeam, Flow, Evaluation, and Automation resources. Use when a user asks Pragma to create, change, configure, test, evaluate, or repair an Expert, team, Flow, Run Dry suite, schedule, trigger, or Automation in the current Pragma project.
portable-bundle-review
A review guide for portable Pragma bundles. A portable bundle is a packaged set of resources intended to work across environments.
pragma-code-review
A code-review guide written in Chinese. It reviews code across correctness, architectural boundaries, risk, and verification.
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…