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 commands/gotempsh/temps/deploy-staticgit clone --depth 1 https://github.com/gotempsh/tempsWhat 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.00307 |
| Opus 5 | $0.00000 | $0.00153 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
deploy-static 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.
What it actually says
deploy:static command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deploy:static (alias: deploy-static)
Deploy static files (tar.gz, zip, or directory)
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--path <path> |
Path to static files archive or directory | - | Yes |
-p, --project <project> |
Project slug or ID | - | No |
-e, --environment <env> |
Target environment name | production |
No |
--environment-id <id> |
Target environment ID | - | No |
--no-wait |
Do not wait for deployment to complete | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | No |
--metadata <json> |
Additional metadata (JSON format) | - | No |
--health-check-path <path> |
HTTP health-check path (must start with "/", e.g. /api/healthz). Overrides .temps.yaml; also updates the uptime monitor. | - | No |
--timeout <seconds> |
Timeout in seconds for --wait | 300 |
No |
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 · 24 lines · 0 tokens per session scan A 71dcd4310f3a
deploy-static is a command published in the GitHub repository gotempsh/temps (700 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 307 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 commands, from other repositories
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
deps-age
Analyze dependency freshness and maintenance activity.
release-prep
Automated release readiness validation.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
project
Follow the project management workflow defined in .agents/skills/project/SKILL.md.
taskrunner-add
Add a task to the autonomous queue.