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/wangke19/gemini-ai-helpers/dev-setupgit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/dev-setup)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/dev-setup"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/dev-setup.svg" alt="Measured on agentmods" 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.00011 | $0.02522 |
| Opus 5 | $0.00005 | $0.01261 |
| Sonnet 5 | $0.00002 | $0.00504 |
| Haiku 4.5 | $0.00001 | $0.00252 |
Grade A, and why
dev-setup 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
olm-team:dev-setup
Synopsis
/olm-team:dev-setup [target-directory]
Description
The olm-team:dev-setup command automates the onboarding process for new OLM team members by setting up all necessary development repositories. It forks repositories (if not already forked), clones them locally with proper remote configuration, and provides educational context about each repository to accelerate team onboarding.
This command helps new developers understand the OLM ecosystem by explaining:
- The difference between upstream (operator-framework) and downstream (openshift) organizations
- The distinction between OLM v0 (traditional) and OLM v1 (next-generation) architectures
- The purpose and relationship of each repository in the development workflow
Implementation
Step 1: Validate Prerequisites
Check for required tools and authentication:
-
Verify GitHub CLI is installed:
which ghIf not installed, provide installation instructions for the user's platform.
-
Verify GitHub CLI authentication:
gh auth statusIf not authenticated, prompt user to run:
gh auth login -
Verify git is installed:
which git -
Get GitHub username:
gh api user --jq '.login'Store this for later use when determining fork URLs.
Step 2: Determine Target Directory
-
If target directory is provided as argument:
- Use the provided directory path
- Expand
~to home directory if present - Create directory if it doesn't exist
-
If no target directory provided:
- Ask user for preferred location using AskUserQuestion tool
- Suggest common options:
~/go/src/github.com/(Go workspace convention)~/src/(Simple source directory)~/code/olm/(OLM-specific directory)
- Create the chosen directory if it doesn't exist
-
Verify directory is writable:
test -w <target-directory> && echo "writable" || echo "not writable"
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 · 325 lines · 11 tokens per session scan A 072a8edbb661
dev-setup is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,522 once invoked, about $0.0001 per session on Opus 5. 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
start-work
Begin work on a Jira issue - creates branch, sets up environment.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
explain
Explain code or concepts clearly with practical examples and analogies.
crossframe-teach
Use CrossFrame Teach to explain CrossFrame concepts in plain Chinese.
dev-loop
Fast development loop for small changes (validate → fix → commit → deploy).
quick
Fastest commit cycle - lint, fix, commit, push (10s).