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/ivan-magda/swift-coding-agent/examplenpx skills add ivan-magda/swift-coding-agent --skill examplegit clone --depth 1 https://github.com/ivan-magda/swift-coding-agentWhat 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.00010 | $0.00157 |
| Opus 5 | $0.00005 | $0.00078 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
example 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.
What it actually says
This is a sample skill file. Skills are stored in skills/{name}/SKILL.md and
provide specialized knowledge that the agent can load on demand via the
load_skill tool.
Frontmatter
Each skill file starts with YAML frontmatter between --- delimiters:
name(optional): defaults to the parent directory namedescription(required): one-line summary shown in the system prompt
Usage
The agent sees skill names and descriptions in its system prompt. When it needs
the full content, it calls load_skill with the skill name. The body below the
frontmatter is returned wrapped in <skill> tags.
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 · 22 lines · 10 tokens per session scan A 9313132c5a03
example is a skill published in the GitHub repository ivan-magda/swift-coding-agent (178 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 157 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-30.
Other skills, from other repositories
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
release-codexbar
CodexBar release: versioning, notarization, appcast, Homebrew, post-release bump.
codexbar
CodexBar read. Provider usage, limits, credits, config health. JSON. No writes.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
release-peekaboo
Peekaboo release: notarization, npm/GitHub release, appcast, verify, closeout.
skill-creator
Autonomously create, test, and optimize skills by detecting reusable patterns in your own work. Use when you notice repeated tool sequences, recurring code patterns across attempts, or insights that should be captured as a packaged skill. Also use to benchmark and iterate on existing skills.