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 docxology/template --skill publishgit clone --depth 1 https://github.com/docxology/templateWrote 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/docxology/template/publish)<a href="https://agentmods.dev/skills/docxology/template/publish"><img src="https://agentmods.dev/badge/skills/docxology/template/publish.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.00052 | $0.00235 |
| Opus 5 | $0.00026 | $0.00118 |
| Sonnet 5 | $0.00010 | $0.00047 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
template-publish 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 3d 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.
What it actually says
SKILL: template-publish
Publishing automation scripts.
Start with docs/guides/publication-runbook.md
for the modular path from rendered project to standalone public GitHub mirror,
real Zenodo DOI, optional mirrors, and archival handoff.
Invocation
uv run python scripts/publish/test_pypi.py
uv run python scripts/publish/verify_install.py
uv run python scripts/publish/publish_project_release.py \
--project templates/<name> --tag v1.0.0 --repo owner/repo
uv run python scripts/publish/upload_template_project.py --project <name>
Related
scripts/publish/AGENTS.md— detailed publishing documentationinfrastructure/publishing/— publishing modules
What ships with it
9 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.
- AGENTS.md 4.2 KB
- export_for_publishing.py 434 B runs code
- publish_project_release.py 5.2 KB runs code
- README.md 6.4 KB
- sync_standalone_mirrors.py 3.0 KB runs code
- test_pypi.py 1.0 KB runs code
- upload_gold_refinement.py 4.1 KB runs code
- upload_template_project.py 5.4 KB runs code
- verify_install.py 3.4 KB runs code
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.
- 3d ago First seen · 31 lines · 52 tokens per session scan A bec26f9d2468
template-publish is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 235 once invoked, about $0.0003 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
release
Execute the weekly release checklist for any uFawkes repo. Use when an increment is ready to ship. Implements the write-once-ship-four-times pattern: README → CHANGELOG → GitHub Release → dev.to → LinkedIn → ufawkes.dev.
ship
Use when a change is ready to land. Runs the full sequence — branch, quality gate, commit, push, PR — so nothing gets skipped.
skill-skill
Create, revise, validate, package, or publish AI skills and rule files. Use as the main entry for the user's skill-authoring workflow, including creating a new SKILL.md, improving an existing rule, and preparing a skill repository. Choose only the requested stage; ordinary product code or content work is outside this…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…