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/fmind/dotfiles/course-developmentnpx skills add fmind/dotfiles --skill course-developmentgit clone --depth 1 https://github.com/fmind/dotfilesWhat 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.00028 | $0.00558 |
| Opus 5 | $0.00014 | $0.00279 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
course-development 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 yesterday.
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop a Technical Course
Turn a technical subject into a course that learners can understand, execute, and finish. Own the learning contract; use hugo for the site, fmind-visuals for slides, and quality-assurance for the test campaign.
Workflow
- Define the learner: State prerequisites, target capability, available time, delivery platform, and accessibility constraints. Remove content that does not advance the target capability.
- Write observable outcomes: Express what the learner will build, diagnose, explain, or decide. Give each module one primary outcome and a completion signal.
- Sequence the journey: Move from a minimal working example through guided practice to an independent lab. Introduce each concept immediately before it is used.
- Make examples executable: Pin dependencies, include expected commands and outputs, keep fixtures small, and run every code path in a clean environment. Never publish placeholder code or unverified APIs.
- Design practice and feedback: Give labs a concrete starting state, success criteria, likely failure modes, and recovery hints. Keep solutions separate enough that learners can attempt the work first.
- Check the human surface: Verify navigation, reading order, keyboard use, contrast, alt text, captions or transcripts, mobile layout, copy-paste behavior, and platform-specific constraints.
- Validate progressively: Test the changed example first, then its lesson, module, navigation, links, and the repository's full gate. Exercise both the instructor and fresh-learner paths.
- Prepare release acceptance: Record the exact candidate, supported platform, test evidence, known limitations, and rollback or correction path. Publishing remains a separate authorization.
Quality Bar
- Prefer one coherent learning path over a catalog of disconnected features.
- Teach the reason and trade-off before adding abstraction.
- Keep sample output deterministic and redact credentials, personal data, and paid-service responses.
- Distinguish local rendering, platform preview, and publicly released evidence.
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.
- yesterday First seen · 37 lines · 28 tokens per session scan A d24e1e493efe
course-development is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 558 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
create-oss-skill
Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.
diataxis
Audit, write, or revise docs under docs/ (or repo equivalent) when the artifact is a tutorial, how-to, reference, or explanation — anything not already a README, CONTRIBUTING, ADR, or CHANGELOG. Forces a Diátaxis mode pick before writing, then loads mode-specific anti-patterns. Use when creating or editing a…
shareable
Draft bite-sized "AI as coworker" wins, experiences, and useful failures for sharing on Google Chat. Use when the user says "draft a shareable about X", "share this win", "add a shareable", "make the technical/layman/one-liner/takeaway version of X", or "format the for posting". Drafts each topic in four registers…
spec-kitty-orchestrator-api-operator
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers: "use orchestrator-api", "build a custom orchestrator", "automate externally", "integrate CI with spec-kitty", "call spec-kitty from another tool", "orchestrator contract", "external…
spk-gate-retrospective
Create or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work.
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.