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/users)<a href="https://agentmods.dev/commands/gotempsh/temps/users"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/users/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/users"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/users.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.00902 |
| Opus 5.5 | $0.00000 | $0.00361 |
| Sonnet 5.5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
users 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
users command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
users
Manage platform users
Subcommands:
list(ls) - List all userscreate(add) - Create a new userme- Show current user inforemove(rm) - Remove a userrestore- Restore a deleted userreset-password- Reset another user's password to a generated temporary one. The user is signed out of every browser session and must choose a new password at next sign-inreset-mfa- Remove another user's MFA (authenticator and recovery codes) after they lost both. The user is signed out of every session and signs in with their password to enroll againrole- Manage user roles
users list (alias: ls)
List all users
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
users create (alias: add)
Create a new user
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
-u, --username <username> |
Username | - | No |
-e, --email <email> |
Email address | - | No |
-p, --password <password> |
Password (if not provided, invite email will be sent) | - | No |
-r, --roles <roles> |
Comma-separated roles (admin, user) | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | No |
users me
Show current user info
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
users remove (alias: rm)
Remove a user
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
User ID | - | Yes |
-f, --force |
Skip confirmation | - | No |
-y, --yes |
Skip confirmation prompts (alias for --force) | - | 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 Changed · +13 lines fb58ca233f1d
- 1mo ago Changed · +13 lines 763bf052b1cc
- 1mo ago First seen · 87 lines · 0 tokens per session scan A 83b7a6c718da
users is a command published in the GitHub repository gotempsh/temps (880 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 902 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
issue-prd-generation
You are generating a comprehensive Product Requirements Document (PRD) for a GitHub issue. This PRD will be passed to a separate AI agent instance with ONLY THIS CONTEXT for implementation. Write with that constraint in mind.
artifact-insight-scan
Analyze the provided project artifacts for missed insights, action items, and follow-ups that should become tracked issues.
start-development
Start the available Software Development Flow in Moira.
ccc-makeover
Score project health with X-Ray, apply the top recommendations in impact order with your OK for each, and show the before and after score. Use when you want the highest-impact project health fixes applied and measured.
signal-planner
Closed-loop autonomy — convert a production/analytics/incident signal into a dependency-ordered issue DAG, execute via /orchestrate, then verify the originating signal is resolved. Event-driven companion to /autopilot.
bootstrap
Bootstrap a new project with design system, CI/CD, i18n, SEO, and deploy pipeline.