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/docxology/template/shellnpx skills add docxology/template --skill shellgit 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/shell)<a href="https://agentmods.dev/skills/docxology/template/shell"><img src="https://agentmods.dev/badge/skills/docxology/template/shell.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.00036 | $0.00498 |
| Opus 5 | $0.00018 | $0.00249 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
template-shell 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.
What it actually says
template-shell
Shell helper scripts for the template framework.
When to use
Load this skill when you need to:
- Run the system health check before a pipeline run
- Reproduce CI locally
- Configure or run backup scripts
- Understand the shell bootstrap sourced by
run.sh
Key scripts
| Script | Purpose |
|---|---|
scripts/shell/health-check.sh |
Pre-flight check (Python, uv, disk, Docker, repo) |
scripts/shell/ci_local.sh |
Local CI reproduction |
scripts/shell/shell_bootstrap.sh |
uv bootstrap + sandbox env vars |
scripts/shell/bash_utils.sh |
Shared helpers (do not source directly in pipeline) |
scripts/shell/backup-daily.sh |
Site-configured daily .hermes rsync tier |
scripts/shell/backup-weekly.sh |
Site-configured weekly repository-cache rsync tier |
scripts/shell/backup-full.sh |
Named, metadata-bearing .hermes/.cache/output snapshot |
scripts/shell/restore-test.sh |
Private-scratch metadata and transfer-consistency verification |
Pitfalls
shell_bootstrap.shis sourced byrun.sh— do not alter itsexportnames.bash_utils.shis for backup/health scripts and integration tests only.- Remote backup helpers require
rsync,ssh, and an SSH alias oruser@hostnamepositional argument (default:backup); they do not use aBACKUP_DESTenvironment variable. - Use matching
--local-root <absolute-dir>arguments for a disposable local full-backup/restore round trip. Local success does not prove off-site availability, creation-time integrity, encryption, retention, or source quiescence.
What ships with it
10 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.
- yesterday First seen · 53 lines · 36 tokens per session scan A 2ed62baf354f
template-shell is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 498 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
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
GitHub CI Fix Debugging
Debug and fix failing GitHub PR checks by inspecting GitHub Actions logs, summarizing failure context, drafting fix plans, and implementing fixes after approval.
pipeline-test-stage-validation
Ensure the CI/CD pipeline includes required test stages. Use when validating that pipeline definitions include unit, integration, and E2E test stages.
cli-scaffolding
Provide CLI commands that scaffold new components, pipelines, tests, and GitOps structures. Use when scaffolding new services, pipeline-spec.yaml, GitOps overlays, or test suites.
e2e-failure-paths
Validate pipeline behavior under failure conditions. Use when simulating test failures, SAST failures, build failures, validating no GitOps update occurs, or checking error propagation.