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/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/docxology/template/publish"><img src="https://agentmods.dev/badge/skills/docxology/template/publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.5 | $0.00021 | $0.00094 |
| Sonnet 5.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 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.
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.9 KB
- export_for_publishing.py 434 B runs code
- publish_project_release.py 5.3 KB runs code
- README.md 7.3 KB
- sync_standalone_mirrors.py 4.1 KB runs code
- test_pypi.py 1.7 KB runs code
- upload_gold_refinement.py 4.1 KB runs code
- upload_template_project.py 5.4 KB runs code
- verify_install.py 1.5 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.
- 1mo ago First seen · 31 lines · 52 tokens per session scan A bec26f9d2468
template-publish is a skill published in the GitHub repository docxology/template (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 235 once invoked, about $0.0002 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-03.
Other skills, from other repositories
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…
ship
Use when a change is ready to land. Runs the full sequence — branch, quality gate, commit, push, PR — so nothing gets skipped.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.