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 skills add fmflurry/settings-opencode --skill show-megit 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/skills/fmflurry/settings-opencode/show-me)<a href="https://agentmods.dev/skills/fmflurry/settings-opencode/show-me"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/show-me/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/skills/fmflurry/settings-opencode/show-me"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/show-me.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.00080 | $0.01149 |
| Opus 5.5 | $0.00032 | $0.00460 |
| Sonnet 5.5 | $0.00016 | $0.00230 |
| Haiku 4.5 | $0.00008 | $0.00115 |
Grade A, and why
show-me 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Help the user understand the current topic of conversation visually. Skip the preamble and keep prose brief.
Default: write an HTML file and open it
Terminal-rendered diagrams read poorly. So unless an exception below applies, produce one self-contained HTML file and open it:
Bash(open /tmp/show-me-{slug}.html)
- Path:
/tmp/show-me-{slug}.html, where{slug}is 2-4 kebab-case words naming the topic. /tmpis the default so the repo working tree stays clean. Write inside the repo only when the user asks to keep the artifact; thendocs/or the path they name.- After opening, leave 1-3 lines in chat: what the file shows and its path. Do not paste the HTML.
Hard constraints on the HTML
- Zero network dependencies. No CDN, no Mermaid script, no Google Fonts, no external CSS or JS. The file must render fully offline. A CDN-loaded diagram library renders as a blank box on a flaky network — build diagrams from plain HTML + CSS instead (flexbox/grid boxes, CSS borders, unicode arrows
▶ ▼ └ ├ ──). - Single file. Inline
<style>in<head>; inline<script>only if interaction genuinely helps. - Match the product's colors, type, spacing, and components. Real labels and real data — never
foo/barplaceholders. - Responsive: readable at desktop width and on mobile. At least one
@mediabreakpoint collapsing multi-column layouts to a single stack. - Monospace blocks for code, trees, and pseudocode; keep them visually distinct from prose.
Pick the smallest form that makes the point
- Diagram — one relationship, flow, or failure chain.
- Infographic — several linked facts that need ranking or comparison.
- Short slide deck — a sequence that only makes sense in order.
Exceptions — answer inline in chat instead
Skip the file only when:
- The user asks for inline output ("inline", "in chat", "no file", "just paste it").
- The whole answer is a copyable snippet or diff under ~10 lines.
- The user is mid-flow and asked a yes/no or one-symbol question.
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.
- 1mo ago First seen · 128 lines · 80 tokens per session scan A 3609411bc692
show-me is a skill published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed 2d ago), licensed MIT. It adds 80 tokens to every session and 1,149 once invoked, about $0.0003 per session on Opus 5.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-09-13.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.