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/backupsgit 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.02004 |
| Opus 5 | $0.00000 | $0.01002 |
| Sonnet 5 | $0.00000 | $0.00401 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
backups 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.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backups command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
backups (alias: backup)
Manage backup schedules and backups
Subcommands:
schedules(schedule) - Manage backup schedulessources(source) - Manage S3 backup sourceslist(ls) - List backups for a scheduleshow- Show backup detailsdelete(rm) - Permanently delete one terminal backupcleanup- Delete backups expired by their schedule retention policyrun-service- Run a backup for an external service
backups schedules (alias: schedule)
Manage backup schedules
Subcommands:
list(ls) - List backup schedulescreate- Create a backup scheduleshow- Show backup schedule detailsenable- Enable a backup scheduledisable- Disable a backup scheduledelete(rm) - Delete a backup schedule
backups schedules list (alias: ls)
List backup schedules
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
backups schedules create
Create a backup schedule
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-n, --name <name> |
Schedule name | - | No |
-t, --type <type> |
Backup type (full, incremental) | - | No |
-s, --schedule <cron> |
Schedule expression (cron format) | - | No |
-r, --retention <days> |
Retention period in days | - | No |
-d, --description <desc> |
Description | - | No |
--s3-source-id <id> |
S3 Source ID | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | No |
backups schedules show
Show backup schedule details
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Schedule ID | - | Yes |
--json |
Output in JSON format | - | 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.
- yesterday First seen · 263 lines · 0 tokens per session scan A 55c8e98af8f5
backups is a command published in the GitHub repository gotempsh/temps (700 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,004 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.