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.
git clone --depth 1 https://github.com/gotempsh/tempsWrote 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/commands/gotempsh/temps/providers)<a href="https://agentmods.dev/commands/gotempsh/temps/providers"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/providers/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/commands/gotempsh/temps/providers"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/providers.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.02247 |
| Opus 5.5 | $0.00000 | $0.00899 |
| Sonnet 5.5 | $0.00000 | $0.00449 |
| Haiku 4.5 | $0.00000 | $0.00225 |
Grade A, and why
providers 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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
providers command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
providers (alias: provider)
Manage Git providers
Subcommands:
list(ls) - List configured Git providersadd- Add a new Git providerremove(rm) - Remove a Git providershow- Show Git provider detailsactivate- Activate a Git providerdeactivate- Deactivate a Git providersafe-delete- Safely delete a Git provider (checks dependencies first)deletion-check- Check if a Git provider can be safely deletedgit- Manage Git providersconnections(conn) - Manage Git provider connections
providers list (alias: ls)
List configured Git providers
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
providers add
Add a new Git provider
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-p, --provider <provider> |
Provider type (github, gitlab, bitbucket, gitea, generic) | - | No |
-n, --name <name> |
Provider name | - | No |
-t, --token <token> |
Personal access token (or Bitbucket access token / app password) | - | No |
--base-url <url> |
Instance base URL (GitLab/Gitea self-hosted; required for gitea) | - | No |
--username <username> |
Bitbucket username (selects app-password auth) | - | No |
--password <password> |
Bitbucket app password (used with --username) | - | No |
--clone-url <url> |
HTTPS clone URL (generic provider) | - | No |
--token-username <username> |
HTTP Basic username for the token (generic; default x-access-token) | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | No |
providers remove (alias: rm)
Remove a Git provider
Options:
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 Changed · +12 lines 4912ee439009
- 1mo ago First seen · 266 lines · 0 tokens per session scan A 805c9ebf4e8f
providers is a command published in the GitHub repository gotempsh/temps (874 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,247 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-09-03.
Other commands, from other repositories
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
rollback-plan
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with rollback plan in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
issue-to-mr-setup
Create an automation that implements GitLab issues when a configurable trigger label is applied. Polls one or more projects deterministically, clones the default branch, starts one OpenHands conversation per label event, then commits, pushes, and opens the merge request itself.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.