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/mismatched/tower/tower-templatenpx skills add mismatched/tower --skill tower-templategit clone --depth 1 https://github.com/mismatched/towerWhat 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.00000 | $0.00915 |
| Opus 5 | $0.00000 | $0.00458 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
tower-template 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tower Template — GitHub Actions Health Checks
Template repo: github.com/mismatched/tower-template — pre-built GitHub Actions workflows for running tower health checks in CI.
Quick Reference
| Goal | Approach |
|---|---|
| Add health checks to a repo | Click Use this template on tower-template, edit targets, commit |
| Check TCP + HTTP + HTTPS + DNS | Use tower-health.yml (every 6h) |
| Check TLS cert expiry | Use tls-cert-expiry.yml (daily at 8am) or add warn_if_expiring via config |
| Manual one-off check | Use workflow_dispatch trigger in either workflow |
| Cert expiry warning | Use config input with a YAML file (composite action doesn't expose warn_if_expiring directly) |
| Install tower action in existing workflow | uses: mismatched/tower@master with tcp, http, https, dns, ws, config, or timeout inputs |
Included Workflows
| Workflow | Schedule | Checks | Inputs |
|---|---|---|---|
tower-health.yml |
Every 6 hours + manual | tcp, http, https, dns |
Quick in-line inputs |
tls-cert-expiry.yml |
Daily at 8am + manual | https (no warn) |
Demonstrates cert-only check |
Action Inputs (mismatched/tower)
| Input | Description | Example |
|---|---|---|
config |
Path to tower config YAML (needs actions/checkout first) |
.github/tower/checks.yml |
tcp |
TCP host:port to check |
example.com:443 |
http |
HTTP/HTTPS URL for status check | https://example.com |
https |
Hostname for TLS cert check | example.com |
dns |
Address to resolve | example.com |
ws |
WebSocket URL to check | wss://example.com/ws |
timeout |
Default timeout duration | 10s (default) |
version |
Tower version to install | latest (default) |
The action fails (exit code 1) if any check returns "OK": false.
Cert Expiry Warnings
The composite action's inline inputs (tcp, http, https, dns, ws) don't support warn_if_expiring. To get cert expiry alerts, use a config file:
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 · 89 lines · 0 tokens per session scan A 9f851af0ce4c
tower-template is a skill published in the GitHub repository mismatched/tower (24 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 915 tokens. 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-08-30.
Other skills, from other repositories
nightly-system-log-review
Review system and application logs for errors/warnings over the last 24 hours, filter known noise, and deliver a consolidated health report via email (AgentMail). Use when running a nightly or periodic system health check, log audit, or error review cron job.
agentic-devops
Production-grade agent DevOps toolkit — Docker, process management, log analysis, and health monitoring. Built by engineers who run production.
alert-rule-troubleshoot
This skill should be used when the user reports that an alert rule is "not firing", "no alert was sent", "the rule didn't trigger", "the rule isn't working", "it should have alerted but didn't", "why didn't I get an alert", "alert rule not firing", or wants to diagnose why a specific alert rule failed to produce an…
generate-message-template
Generate or modify Nightingale (n9e) alert notification message templates. Use when the user asks to write a notification template, change the message format, add hostname/recovery value/severity, or create DingTalk/Feishu/Lark/email/SMS/voice templates.
ops-troubleshooting
This skill should be used when the user asks to "troubleshoot", "diagnose", "debug alert", "investigate incident", "locate a fault", "investigate an alert", "diagnose a problem", "fix an issue", "check alerts", "analyze alerts", "root cause analysis", "check metrics", "check logs", or discusses…
doc-qa
This skill should be used when the user asks "how-to" or factual questions about Nightingale (n9e) — UI/where-to-click, business groups/subscription rules/mute rules/edge mode, Token usage, notification pipeline, self-healing trigger conditions; OR about categraf input plugin field meanings, metric names, defaults…