Borrowing it
Nothing to install: this file belongs to chiKeka/bricolage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chiKeka/bricolage/main/CLAUDE.mdgit clone --depth 1 https://github.com/chiKeka/bricolageWrote 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/instructions/chikeka/bricolage/claude-md)<a href="https://agentmods.dev/instructions/chikeka/bricolage/claude-md"><img src="https://agentmods.dev/badge/instructions/chikeka/bricolage/claude-md.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.01213 | $0.01213 |
| Opus 5 | $0.00607 | $0.00607 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
bricolage CLAUDE.md 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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bricolage — Agent Toolkit
You are helping a user with the Bricolage Agent Toolkit — a collection of autonomous agents that assemble free-tier resources into working outcomes.
Bricolage (from Lévi-Strauss) is the craft of making do with what's at hand. That is what these agents do: they read a catalog of free resources, pick the ones that fit a user's goal, and combine them into something that runs.
What This Repo Is
Bricolage is a domain-agnostic protocol for turning free resources into outcomes. It ships with a compute domain (cloud services for building software) but can self-expand into any domain - education, health, finance, research - as users bring new goals.
The agents:
- Plan which free resources to combine for a goal
- Guide users through acquiring access (accounts, API keys, enrolments)
- Assemble acquired resources into working outcomes
- Discover new domains and resources when a goal doesn't fit existing domains
How To Help The User
- Check state first: Call
ubc_statusandubc_domainsto see what's configured - If new user: Walk them through setup - explain what Bricolage is, show domains and patterns
- If returning user: Pick up where they left off based on state
- If goal doesn't match a domain: Delegate to the discovery agent
Note on tool names: MCP tool names keep the
ubc_prefix from when this system was called Universal Basic Compute. The prefix is a stable token — renaming it would break every agent prompt, slash command, and downstream client.
Available Agents (in /agents/)
| Agent | Purpose | When to use |
|---|---|---|
| master | Orchestrates everything | Default - delegates to others |
| planner | Selects resources for a goal | When user describes a goal |
| guide | Walks through access acquisition | When setting up a resource |
| assembler | Builds outcomes from resources | After all resources acquired |
| discovery | Finds resources, creates domains | When goal doesn't fit a domain |
| infra | Sets up agent infrastructure | Compute domain only |
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.
- 6d ago First seen · 96 lines · 1,213 tokens per session scan A 0d4490dd723f
bricolage CLAUDE.md is an instructions file published in the GitHub repository chiKeka/bricolage (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,213 tokens to every session, about $0.0061 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.