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/joris887/exosuit/skill-createnpx skills add joris887/exosuit --skill skill-creategit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/skill-create)<a href="https://agentmods.dev/skills/joris887/exosuit/skill-create"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/skill-create.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 | $0.00020 | $0.01618 |
| Opus 5 | $0.00010 | $0.00809 |
| Sonnet 5 | $0.00004 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
skill-create 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 3d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-create
Analyzing repository and generating technology skills.
1. Scan Repository
Identify technologies, frameworks, and tools in use:
1a. Parse dependency files
Scan for all dependency/config files in the project:
package.json,pyproject.toml,Cargo.toml,Package.swiftgo.mod,pom.xml,build.gradle,Gemfile,composer.json.pre-commit-config.yaml, CI configuration files
1b. Scan imports and usage
Identify major technology areas by scanning source code imports and configuration files.
1c. Check existing skills
Read .claude/skills/SKILLS_INVENTORY.md to avoid creating duplicates.
2. Classify Technologies
Categorize each technology by impact and relevance:
| Category | Examples | Skill Priority |
|---|---|---|
| Core Framework (>20% of codebase) | React, Django, Rails, SwiftUI | High — create skill + reference doc |
| Major Library (significant usage) | SQLite, Redis, Prisma | Medium — create skill |
| Build/Dev Tool (development workflow) | webpack, jest, ruff | Low — create skill if complex |
| Minor Dependency (small usage) | lodash, httpx, pydantic | Skip — standard usage, no skill needed |
Decision Criteria for Reference Documents
Create reference docs co-located with the skill (.claude/skills/<tech-name>/references/) when:
- Technology is core (>20% of codebase interaction)
- API is complex with project-specific patterns
- Version-specific gotchas exist that an LLM would miss
- Official documentation is large and we use a specific subset
Co-locating references with skills keeps everything self-contained and allows relative path references from SKILL.md.
Skip reference doc when:
What ships with it
2 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.
- 3d ago First seen · 207 lines · 20 tokens per session scan A 8c43aab7f5a2
skill-create is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 14d ago), licensed MIT. It adds 20 tokens to every session and 1,618 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
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…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
linkedin-post
You take a YouTube video transcript and produce a single LinkedIn post draft.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
source-command-ccguide-daily
Daily update check — official Anthropic docs diff + guide/CC releases digest.