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/dot/skillifynpx skills add fmind/dot --skill skillifygit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/skillify)<a href="https://agentmods.dev/skills/fmind/dot/skillify"><img src="https://agentmods.dev/badge/skills/fmind/dot/skillify.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.00038 | $0.00819 |
| Opus 5 | $0.00019 | $0.00409 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
skillify 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skillify
Capture what this session learned as a skill the next session can run without the conversation. The agent-skills skill owns the package format and validation; this skill owns the extraction and the writing.
Workflow
- Extract from the session: the goal, the user's trigger phrases, the exact commands that worked (with flags), the decisions and why, the dead ends, and the tools required; drop session-specific paths, one-off values, and secrets.
- Check the catalog:
skills listandskills list -g, then read any neighbor with an overlapping description; extend it when the workflow is the same, write a new skill only for a distinct trigger, and link neighbors instead of copying them. - Choose the scope:
- Global (reusable, tool-generic):
~/.agents/skills/<name>/, theskills/directory of the dot repository; add its CLI names toskills/contracts.json, then runmise run check:skillsandmise run testthere. - Local (repository-specific commands, data, or conventions):
.agents/skills/<name>/in the project; add.claude/skills -> ../.agents/skillsif missing per agent-project.
- Global (reusable, tool-generic):
- Write from the template: copy skill.md and apply the Skill Authoring Limits of the global
~/.agents/AGENTS.mdfor name, description, size, shape, and placement; long configs and examples go toreferences/. - Validate: frontmatter
nameequals the directory; every link resolves; every required tool is named in the body;gh skill publish --dry-run <parent-dir>passes for a global skill. - Test once: run the skill's steps in a scratch directory or on the current repository and fix what does not reproduce; a skill that was never executed is a draft.
- Report: the path, the description, the scope, and whether the routing probes in
dot/testdata/skills/need a new prompt for the skill.
Extracting from AGENTS.md
When AGENTS.md grows past rules and layout, move each multi-step section into its own local skill, leave a one-line pointer ("see .agents/skills/<name>"), and re-run readme-agents.
What ships with it
1 file 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.
- yesterday First seen · 42 lines · 38 tokens per session scan A 83382839178c
skillify is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 819 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.