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 Kevin-Liu-01/Agent-Machines --skill skill-creatorgit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/skill-creator)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/skill-creator"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/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/kevin-liu-01/agent-machines/skill-creator"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/skill-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium MCP Rug Pull · line 24 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 98 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00099 | $0.01059 |
| Opus 5 | $0.00049 | $0.00530 |
| Sonnet 5 | $0.00020 | $0.00212 |
| Haiku 4.5 | $0.00010 | $0.00106 |
Grade A, and why
skill-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 9d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Create new skills and iteratively improve them. Wiki-aware variant that integrates with Kevin's LLM Wiki.
Wiki-First Protocol
Before creating any skill:
- Check the wiki. Read
wiki/_index.mdand search for pages related to the skill's domain. Existing wiki pages contain Kevin's compiled knowledge and preferences. - Check skills.sh. Use the
find-skillsskill to search for existing upstream skills. Prefer adapting an upstream skill over building from scratch. - Check installed skills. Scan
skills/personal/,skills/claude/, andskills/dedalus/for overlap. Don't create a skill that duplicates an existing one.
After creating a skill:
- Update
wiki/tools/skills-sh.md— Add the new skill to the installed skills table - Update
AGENTS.md— Add to the installed skills table in the Skills section - Update
wiki/log.md— Record what was created and why - Cross-reference — Update related wiki pages with links to the new skill
- Rebuild index — Run
npx tsx scripts/build-index.ts
Skill Creation Process
1. Capture Intent
- What should this skill enable the agent to do?
- When should it trigger? (specific user phrases and contexts)
- What's the expected output format?
- Does an upstream skill on skills.sh already cover this? (check first)
2. Interview and Research
- Ask about edge cases, input/output formats, success criteria, dependencies
- Check wiki pages for existing knowledge on the topic
- Check skills.sh for similar skills that could be adapted
3. Write the SKILL.md
Install Cursor/personal skills to skills/personal/<name>/SKILL.md (loaded through the ~/.cursor/skills symlink). Required structure:
---
name: skill-name
description: What it does and when to trigger. Be pushy — include specific trigger phrases.
---
Skill anatomy:
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter (name, description required)
│ └── Markdown instructions
└── Bundled Resources (optional)
├── scripts/ - Executable code for deterministic tasks
├── references/ - Docs loaded into context as needed
└── assets/ - Templates, icons, fonts
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.
- 9d ago First seen · 116 lines · 99 tokens per session scan A 84479a445a77
skill-creator is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 1,059 once invoked, about $0.0005 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-03.
Other skills, from other repositories
holix-cron
Schedule recurring agent tasks via Holix built-in gateway cron (not crontab or custom scripts).
21-day-self-interview
A 21-night guided self-reflection routine in which an agent asks three questions each night, remembers the answers, and reflects on them at key points.
tomtom
TomTom Maps MCP integration — search, routing, traffic, maps, POIs, and EV via hosted endpoint.
map-your-market
Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences, then synthesizes everything into a positioning framework showing who your ICP is, what they say out loud, and exactly how…
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
jikegongyuan-perspective
A writing guide based on GeekPark, a Chinese technology publication and entrepreneur community focused on AI, products, startups, and innovation.