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/ip-access)<a href="https://agentmods.dev/commands/gotempsh/temps/ip-access"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/ip-access/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/ip-access"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/ip-access.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.01366 |
| Opus 5.5 | $0.00000 | $0.00546 |
| Sonnet 5.5 | $0.00000 | $0.00273 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
ip-access 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ip-access command reference
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
ip-access (alias: ipa)
Manage instance-wide IP access control rules, and per-project lists (ip-access project)
Subcommands:
list(ls) - List all IP access control rulescreate(add) - Create a new IP access control ruleshow- Show IP access control rule detailsupdate- Update an IP access control ruleremove(rm) - Delete an IP access control rulecheck- Check if an IP address is blockedproject- Allow or deny IP ranges for one project or environment
ip-access list (alias: ls)
List all IP access control rules
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--json |
Output in JSON format | - | No |
ip-access create (alias: add)
Create a new IP access control rule
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--ip <ip_or_cidr> |
IPv4 or IPv6 address or CIDR range (e.g., "192.168.1.1", "10.0.0.0/24", or "2001:db8::/32") | - | No |
--action <action> |
Action to take: "allow" or "deny" | - | No |
--description <desc> |
Optional description/reason for the rule | - | No |
-y, --yes |
Skip confirmation prompts (for automation) | - | No |
ip-access show
Show IP access control rule details
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Rule ID | - | Yes |
--json |
Output in JSON format | - | No |
ip-access update
Update an IP access control rule
Options:
| Flag | Description | Default | Required |
|---|---|---|---|
--id <id> |
Rule ID | - | Yes |
--ip <ip> |
New IP address or CIDR range | - | No |
--action <action> |
New action: "allow" or "deny" | - | No |
--description <desc> |
New description/reason | - | 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 Changed · +65 lines 8affb6f435c1
- 1mo ago First seen · 89 lines · 0 tokens per session scan A 8eca74a877bc
ip-access is a command published in the GitHub repository gotempsh/temps (846 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,366 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
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
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.
secrets-audit
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with secrets audit in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.