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 skills/geekbot-com/geekbot-cli/geekbot-setupnpx skills add geekbot-com/geekbot-cli --skill geekbot-setupgit clone --depth 1 https://github.com/geekbot-com/geekbot-cliWrote 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/skills/geekbot-com/geekbot-cli/geekbot-setup)<a href="https://agentmods.dev/skills/geekbot-com/geekbot-cli/geekbot-setup"><img src="https://agentmods.dev/badge/skills/geekbot-com/geekbot-cli/geekbot-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 | $0.00035 | $0.01189 |
| Opus 5 | $0.00017 | $0.00594 |
| Sonnet 5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
geekbot-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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Geekbot — Setup
Goal: get the user fully ready — CLI installed, CLI authenticated, and a clear "you're ready" or "here's what to do next" message at the end.
Steps
-
Check the CLI is on
$PATH:command -v geekbot -
Install if missing:
npm install -g geekbot-cliIf
npmisn't available, mentionbun install -g geekbot-clias an alternative and let the user run it themselves. -
Verify the install:
geekbot --version -
Check auth (does not prompt):
geekbot auth status- If
data.authenticated == true→ skip to step 6. - Otherwise → step 5.
- If
-
Authenticate via OAuth — you drive
geekbot auth loginyourself. Do NOT tell the user to run anything in their shell. Do NOT ask for an API key. The CLI's loopback flow only exposes a public authorize URL (no secrets), and writes the resultingcli_*token to the user's OS keychain on their own machine when the flow completes.Procedure:
a. Start the login command in the background. Use Bash with
run_in_background: trueso you can read the verification URL while the CLI waits on its loopback listener. Always pass--no-browser— you can't pick the user's browser for them, especially on WSL wherexdg-openwould launch the Linux default rather than the browser that holds the user's Geekbot dashboard session.geekbot auth login --no-browser --ttl-days 30b. Capture the authorize URL. Call
BashOutputon the background shell once, then again a second later if needed, until stderr contains a line that starts withhttps://and a URL pointing at/v2/authorize?.... The CLI prints a block like:Listening on http://127.0.0.1:<port>/callback for the OAuth callback… Open this URL in a browser to sign in: https://oauth.geekbot.com/v2/authorize?...&state=...&code_challenge=... Only open it ONCE — the state is single-use.
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.
- 3d ago First seen · 127 lines · 35 tokens per session scan A 461e3189e658
geekbot-setup is a skill published in the GitHub repository geekbot-com/geekbot-cli (20 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,189 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
review-agentic-workflows
Review agentic workflow changes for correctness, security posture, and optimization opportunities with compile, validation, and audit evidence.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
diagnostic-stem-delivery
Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.