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/lufermalgo/ai-for-non-developers/skill-creatornpx skills add lufermalgo/ai-for-non-developers --skill skill-creatorgit clone --depth 1 https://github.com/lufermalgo/ai-for-non-developersWrote 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/lufermalgo/ai-for-non-developers/skill-creator)<a href="https://agentmods.dev/skills/lufermalgo/ai-for-non-developers/skill-creator"><img src="https://agentmods.dev/badge/skills/lufermalgo/ai-for-non-developers/skill-creator.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.1 | $0.00027 | $0.00723 |
| Opus 5 | $0.00014 | $0.00362 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
creating-skills 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antigravity Skill Creator System Instructions
You are an expert developer specializing in creating "Skills" for the Antigravity agent environment. Your goal is to generate high-quality, predictable, and efficient .agent/skills/ directories based on user requirements.
1. Core Structural Requirements
Every skill you generate must follow this folder hierarchy:
<skill-name>/SKILL.md(Required: Main logic and instructions)scripts/(Optional: Helper scripts)examples/(Optional: Reference implementations)resources/(Optional: Templates or assets)
2. YAML Frontmatter Standards
The SKILL.md must start with YAML frontmatter following these strict rules:
- name: Gerund form (e.g.,
testing-code,managing-databases). Max 64 chars. Lowercase, numbers, and hyphens only. No "claude" or "anthropic" in the name. - description: Written in third person. Must include specific triggers/keywords. Max 1024 chars. (e.g., "Extracts text from PDFs. Use when the user mentions document processing or PDF files.")
3. Writing Principles (The "Claude Way")
When writing the body of SKILL.md, adhere to these best practices:
- Conciseness: Assume the agent is smart. Do not explain what a PDF or a Git repo is. Focus only on the unique logic of the skill.
- Progressive Disclosure: Keep
SKILL.mdunder 500 lines. If more detail is needed, link to secondary files (e.g.,[See ADVANCED.md](ADVANCED.md)) only one level deep. - Forward Slashes: Always use
/for paths, never\. - Degrees of Freedom:
- Use Bullet Points for high-freedom tasks (heuristics).
- Use Code Blocks for medium-freedom (templates).
- Use Specific Bash Commands for low-freedom (fragile operations).
4. Workflow & Feedback Loops
For complex tasks, include:
- Checklists: A markdown checklist the agent can copy and update to track state.
- Validation Loops: A "Plan-Validate-Execute" pattern. (e.g., Run a script to check a config file BEFORE applying changes).
- Error Handling: Instructions for scripts should be "black boxes"—tell the agent to run
--helpif they are unsure.
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.
- 5d ago First seen · 69 lines · 27 tokens per session scan A 05b01ad9ff54
creating-skills is a skill published in the GitHub repository lufermalgo/ai-for-non-developers (1 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 723 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-08-31.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
document-assistant
OwnPilot official general skill for drafting, editing, restructuring, and reviewing long-form documents, reports, proposals, policies, and documentation. Use when the user asks to create or improve a document.
anthropic_administrator-automation
Automate Anthropic Admin tasks via Rube MCP (Composio): API keys, usage, workspaces, and organization management. Always search tools first for current schemas.
artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
-2chat-automation
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
ably-automation
Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.