What is geekbot-setup?

A setup workflow for the Geekbot command-line tool, which manages team standups, reports, and polls. It checks installation, authentication, and readiness.

Use it when preparing Geekbot for the first time or checking why Geekbot commands cannot access the account.

It removes the need to manually verify whether the command-line tool is installed and signed in correctly.

geekbot-setup — Skill for Claude Code and Cursor by geekbot-com

Install

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.

Any agent

npx skills add geekbot-com/geekbot-cli --skill geekbot-setup

Clone the repo

git clone --depth 1 https://github.com/geekbot-com/geekbot-cli

Made for: Claude Code, Cursor.

Or install geekbot, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/geekbot-com/geekbot-cli/geekbot-setup/github.svg)](https://agentmods.dev/skills/geekbot-com/geekbot-cli/geekbot-setup)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,189 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00035	$0.01189
Opus 5.5	$0.00014	$0.00476
Sonnet 5.5	$0.00007	$0.00238
Haiku 4.5	$0.00003	$0.00119

Measured 1mo ago against content hash 461e3189e658, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/geekbot/skills/geekbot-setup/SKILL.md · 127 lines

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-cli
```
If npm isn't available, mention bun install -g geekbot-cli as 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.
Authenticate via OAuth — you drive geekbot auth login yourself. 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 resulting cli_* 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: true so 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 where xdg-open would launch the Linux default rather than the browser that holds the user's Geekbot dashboard session.
```
geekbot auth login --no-browser --ttl-days 30
```
b. Capture the authorize URL. Call BashOutput on the background shell once, then again a second later if needed, until stderr contains a line that starts with https:// 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.
```

Read the full file on GitHub · 127 lines

Changes

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.

1mo ago First seen · 127 lines · 35 tokens per session scan A 461e3189e658

Subscribe to this mod's changes

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.0001 per session on Opus 5.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.

Productivity Project management

gsd-ns-manage

config workspace | workstreams thread update ship inbox.

open-gsd/gsd-core · 16 tokens

feature-prioritisation

Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…

mohitagw15856/pm-claude-skills · 103 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

triage-inbox

Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…

pedrohcgs/claude-code-my-workflow · 132 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

cs-escalation-brief

Redacta un informe de escalada estructurado para una cuenta de cliente en riesgo. Úsalo cuando una cuenta haya escalado, cuando un cliente amenace con cancelar, cuando un problema de cliente P1 requiera atención ejecutiva, o cuando prepares un plan de retención interno. Produce un informe de escalada preciso con…

mohitagw15856/pm-claude-skills · 94 tokens