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.
git clone --depth 1 https://github.com/fmflurry/settings-opencodeWrote 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/commands/fmflurry/settings-opencode/skill-create)<a href="https://agentmods.dev/commands/fmflurry/settings-opencode/skill-create"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/skill-create/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/commands/fmflurry/settings-opencode/skill-create"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/skill-create.svg" alt="Reviewed on agentmods" width="80" 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.00006 | $0.00424 |
| Opus 5.5 | $0.00002 | $0.00170 |
| Sonnet 5.5 | $0.00001 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 26d 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.
This is a copy
86% identical to skill-create — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Skill Create Command
CC: no dedicated subagent — the primary agent runs these steps directly.
Analyze git history to generate OpenCode skills: $ARGUMENTS
Your Task
- Analyze commits - Pattern recognition from history
- Extract patterns - Common practices and conventions
- Generate SKILL.md - Structured skill documentation
Analysis Process
Step 1: Gather Commit Data
# Recent commits
git log --oneline -100
# Commits by file type
git log --name-only --pretty=format: | sort | uniq -c | sort -rn
# Most changed files
git log --pretty=format: --name-only | sort | uniq -c | sort -rn | head -20
Step 2: Identify Patterns
Commit Message Patterns:
- Common prefixes (feat, fix, refactor)
- Naming conventions
- Co-author patterns
Code Patterns:
- File structure conventions
- Import organization
- Error handling approaches
Review Patterns:
- Common review feedback
- Recurring fix types
- Quality gates
Step 3: Generate SKILL.md
# [Skill Name]
## Overview
[What this skill teaches]
## Patterns
### Pattern 1: [Name]
- When to use
- Implementation
- Example
### Pattern 2: [Name]
- When to use
- Implementation
- Example
## Best Practices
1. [Practice 1]
2. [Practice 2]
3. [Practice 3]
## Common Mistakes
1. [Mistake 1] - How to avoid
2. [Mistake 2] - How to avoid
## Examples
### Good Example
```[language]
// Code example
```
### Anti-pattern
```[language]
// What not to do
```
Output
Creates:
skills/[name]/SKILL.md- Skill documentation
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.
- 26d ago Changed · +2 lines ecbc35d23bfe
- 1mo ago First seen · 104 lines · 6 tokens per session scan A 69b2633cf86d
skill-create is a command published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 424 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to skill-create, differing in 42 lines, and is treated as a copy.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…