bareclaw: Command for Claude Code

.claude/commands/setup.md

setup is a command for Claude Code from elliotbonneville/bareclaw. It costs 0 tokens per session (419 once invoked), scanned A, original, MIT.

A first-run setup guide for BAREclaw, an application that can connect to services such as Telegram or HTTP. It checks environment settings and helps personalize the assistant’s behavior file.

In plain words
What is it for?
Use it to create or complete the .env file, configure Telegram or HTTP authentication, and optionally add personal instructions to SOUL.md.
Why use it?
It reduces setup mistakes and makes sure required access tokens, allowed users, and personal preferences are configured before use.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is elliotbonneville/bareclaw's own configuration. It tells Claude Code how to work on bareclaw itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bareclaw configures →

Reuse

Borrowing it

Nothing to install: this file belongs to elliotbonneville/bareclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/elliotbonneville/bareclaw/main/.claude/commands/setup.md
Clone the repo
git clone --depth 1 https://github.com/elliotbonneville/bareclaw

Made for: Claude Code.

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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/elliotbonneville/bareclaw/setup/github.svg)](https://agentmods.dev/commands/elliotbonneville/bareclaw/setup)
Your own site
<a href="https://agentmods.dev/commands/elliotbonneville/bareclaw/setup"><img src="https://agentmods.dev/badge/commands/elliotbonneville/bareclaw/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.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/elliotbonneville/bareclaw/setup"><img src="https://agentmods.dev/badge/commands/elliotbonneville/bareclaw/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 419 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00419
Opus 5.5 $0.00000 $0.00168
Sonnet 5.5 $0.00000 $0.00084
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

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

.claude/commands/setup.md · 38 lines

What it actually says

Guide the user through setting up their BAREclaw instance. This is a first-run setup flow.

Steps

1. Check prerequisites

Verify that the .env file exists and has the required variables configured:

  • BARECLAW_TELEGRAM_TOKEN (if they want Telegram)
  • BARECLAW_ALLOWED_USERS (required for Telegram)
  • BARECLAW_HTTP_TOKEN (recommended for HTTP auth)

If .env doesn't exist, copy .env.example and walk them through filling it in.

2. Personalize SOUL.md

Read the existing SOUL.md — it defines your core personality and engineering principles. Ask the user if they want to add a personal section at the top. Things to ask about:

  • Name: Do they want to call you something specific?
  • Tone adjustments: More casual? More technical? Different from the defaults?
  • Boundaries: Things you should never do without asking (e.g., git push, delete files, deploy to prod)
  • Context: What they're working on, what kind of tasks they'll typically send you

If they want changes, add a ## Personal section near the top of SOUL.md with their preferences. Don't overwrite the existing personality or engineering principles — those are the project defaults.

If they're happy with the defaults, move on.

3. Install heartbeat

Run bash heartbeat/install.sh to set up the heartbeat scheduled job. Confirm it installed successfully.

4. Start the server

If not already running, start with npm run dev. Verify it starts successfully.

5. Test connectivity

If Telegram is configured, send a test message via POST /send to confirm the bot can reach them.

Important

  • Be conversational during setup — this is the user's first impression of their agent.
  • Don't dump all questions at once. Ask them one topic at a time.
  • If they seem impatient, offer to use sensible defaults and let them customize later.
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.

  1. 2mo ago First seen · 38 lines · 0 tokens per session scan A e5ffc50009ae

Subscribe to this mod's changes

setup is a command published in the GitHub repository elliotbonneville/bareclaw (22 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 419 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.

Related

setup compared with commands from other repositories

setup next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
setupelliotbonneville/bareclawCommand228mo agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code