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/project-groups)<a href="https://agentmods.dev/commands/gotempsh/temps/project-groups"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/project-groups/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/project-groups"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/project-groups.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.02443 |
| Opus 5.5 | $0.00000 | $0.00977 |
| Sonnet 5.5 | $0.00000 | $0.00489 |
| Haiku 4.5 | $0.00000 | $0.00244 |
Grade A, and why
project-groups 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-groups command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
project-groups (alias: pg)
Manage Projects (what the console calls a Project): groups of services that ship together and share a repository, variables and path routes. A service is what the projects command manages; the services command manages databases and caches, not these.
Subcommands:
list(ls) - List projects (groups) and their servicesshow(get) - Show a project (group), by slug or idcreate(new) - Create a project (group), optionally with servicesupdate(edit) - Rename a project (group) or change its descriptiondelete(rm) - Delete a project (group); its services keep running as standalone servicesadd- Add services to a project (group), by slug or id as listed byprojects list; moves them out of any other projectremove- Remove a service (slug or id) from a project (group); it becomes a standalone servicerepo- The repository a project deploys its services from (monorepos)import- Scan the project's repository and add its apps as services that follow itfollow- Make a service follow the project's repository and branch (keeps its directory)unfollow- Stop a service following the project's repository; it keeps its current settingsroutes- Serve a path of one service's domains from another service (e.g. /api → backend)vars- Variables shared by every service in a project (group)
project-groups list (alias: ls)
List projects (groups) and their services
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--page <n> |
Page number (default 1) | - | No |
--per-page <n> |
How many per page (default 100, at most 100) | - | No |
--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.
- 2d ago First seen · 256 lines · 0 tokens per session scan A b362fa64f1d9
project-groups is a command published in the GitHub repository gotempsh/temps (848 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,443 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-10-15.
Other commands, from other repositories
terraform-scaffold
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with terraform scaffold in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
cost-optimize
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with cost optimize in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
cost-optimize
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with cost optimize in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
monitor-setup
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with monitor setup in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
monitor-setup
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with monitor setup in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
snowdreamtech.init
Proxy for snowdreamtech.init.md.