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/technical-publishingnpx skills add fmind/dot --skill technical-publishinggit 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/technical-publishing)<a href="https://agentmods.dev/skills/fmind/dot/technical-publishing"><img src="https://agentmods.dev/badge/skills/fmind/dot/technical-publishing.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.1 | $0.00032 | $0.00633 |
| Opus 5 | $0.00016 | $0.00316 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
technical-publishing 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 2d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Technical Articles
Publish technical articles from package sources through review, canonical web export, and channel copy. Third-party documentation sites and static websites use hugo, software releases use release, and standalone documents use typst.
pub init article <slug> # scaffold package directories and draft
pub check <package> --publish-ready # offline gate; readiness, not authorization
pub publish <package> --site <site-directory> # export to canonical site; --dry-run previews
Workflow
- Package pipeline: work inside the article package layout (
draft.txt -> article.md -> canonical site -> posts/);draft.txtcontains raw notes that agents never edit; see Package layout. - Voice and boundaries: adhere to the editorial voice in Voice and identity; agree the register before drafting; never invent anecdotes, clients, or metrics; keep published articles immutable.
- Visuals: explanatory diagrams follow fmind-visuals and d2 using the light-surface theme; store
.d2sources beside rendered PNGs. - Canonical export: export to the canonical site only when authorized; live article corrections belong on the site.
- Channel copy: prepare channel adaptations in
posts/(LinkedIn, X, Bluesky, Medium); channels are posted by hand, never automated or scheduled.
Gotchas
- Channel automation: only canonical site export is automated; all other channels are manual copy-paste.
- Immutable published copy: once published, package copy is historical; live corrections stay on the published site.
- Anti-slop enforcement: avoid hype lead-ins, decorative lists, and empty corporate summaries; maintain the direct first-person voice.
Documentation
- Package layout · Voice and identity
- Companion skills: fmind-visuals (diagram theme and brand), d2 (diagram source), hugo (docs sites), release (software releases), typst (standalone documents).
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.
- 2d ago First seen · 40 lines · 32 tokens per session scan A 8f7b5d73bce0
technical-publishing is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 633 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.
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.
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.