setup

A guided setup procedure for Bricolage, including checking available domains, showing patterns, and tracking access and progress. In this context, a domain is a subject area with resources and reusable ways of working.

In plain words
What is it for?
Starting Bricolage, checking existing setup progress, selecting a domain and pattern, storing access details, and updating status.
Why use it?
It helps a new user choose the right subject area and gather the resources needed before building.

Command

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.

agentmods
npx agentmods add commands/chikeka/bricolage/setup
Clone the repo
git clone --depth 1 https://github.com/chiKeka/bricolage
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 180 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00180
Opus 5 $0.00000 $0.00090
Sonnet 5 $0.00000 $0.00036
Haiku 4.5 $0.00000 $0.00018

Measured yesterday against content hash a563698e0310, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

commands/setup.md · 16 lines

What it actually says

Help the user get started with Bricolage.

  1. Call ubc_domains to show available domains
  2. Call ubc_status to check if there's any existing progress
  3. Ask the user what they want to accomplish
  4. Determine which domain fits their goal:
    • If a domain exists, show its patterns via ubc_patterns
    • If no domain fits, explain that the discovery agent can research and create one
  5. For the chosen domain and pattern, walk through acquiring each resource:
    • Call ubc_resource_guide for detailed instructions
    • Store tokens via ubc_store_access
    • Track progress via ubc_update_status
  6. Once all resources are acquired, let the user know they're ready to build

Be friendly and patient. Assume the user is not technical. Explain everything step by step.

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. yesterday First seen · 16 lines · 0 tokens per session scan A a563698e0310

Subscribe to this mod's changes

setup is a command published in the GitHub repository chiKeka/bricolage (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 180 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-31.