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/gettalon/talon-plugins/create-skillnpx skills add gettalon/talon-plugins --skill create-skillgit clone --depth 1 https://github.com/gettalon/talon-pluginsWhat 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.00047 | $0.00955 |
| Opus 5 | $0.00023 | $0.00477 |
| Sonnet 5 | $0.00009 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
create-skill 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 2d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill — Domain Workflow Designer
Design a SKILL.md file that teaches an agent how to complete a specific domain task through a structured, repeatable workflow.
What Makes a Good Skill
A skill is NOT just instructions. It's a repeatable workflow with:
- Clear trigger conditions (when to activate)
- Step-by-step checklist (track progress)
- Specific tool calls at each step (what data to gather)
- Validation/sanity checks (catch errors before presenting)
- Structured output format (consistent results)
A well-structured skill tells the agent exactly which tools to call, what data to extract, how to calculate, how to validate, and how to present results.
Process
Step 1: Understand the Task
Ask one at a time:
-
What task does this skill perform?
- e.g., "Analyze a company's competitive moat"
- e.g., "Review a pull request for security issues"
- e.g., "Generate a weekly project status report"
-
When should the agent activate this skill?
- What trigger phrases or questions activate it?
- e.g., "Triggers on: moat analysis, competitive advantage, defensibility, economic moat"
-
What tools does the agent need?
- web_search, web_fetch, get_financials, read_file, shell, browser, etc.
- What APIs or data sources are required?
-
What does the output look like?
- Tables, prose, structured report, checklist?
- Show an example of ideal output if possible.
Step 2: Design the Workflow
Break the task into 4-8 sequential steps. For each step define:
- What to do: Clear action (e.g., "Call get_financials with...")
- What data to extract: Specific fields/values
- Fallback: What to do if data is missing
- Validation: How to check the step succeeded
Design patterns to follow:
- Each step should produce data the next step consumes
- Include cross-validation between steps (e.g., compare two independent estimates)
- Cap assumptions (e.g., "growth rate capped at 15%")
- Always include a validation step before final output
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.
- 2d ago First seen · 123 lines · 47 tokens per session scan A f011a6bb24dc
create-skill is a skill published in the GitHub repository gettalon/talon-plugins (6 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 955 once invoked, about $0.0002 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
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends AIPex's capabilities with specialized knowledge, workflows, or tool integrations.
build-plugin
Complete plugin development workflow: build, test, icon, troubleshoot, and setup. Use when the user wants to build a plugin, create a plugin, troubleshoot issues, add icons, or install/configure plugins. Triggers on: build plugin, create plugin, develop plugin, new plugin, plugin icon, troubleshoot, debug, setup…
unicli-explorer
Create new Uni-CLI adapters by exploring websites and APIs. Use when adding support for a new site, desktop app, or service that unicli doesn't cover yet.
website-explorer
Discover website capabilities from user behaviors. Learn APIs and automate workflows.
context-engineering
Improve cloakbrowser-mcp agent instructions, skill routing, durable decisions, task context, or handoffs only when the user explicitly requests context optimization, migration, stale-guidance repair, or recoverable session handoff. Align guidance with current bridge code, tests, configuration, docs, and delivery…