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 agents/chikeka/bricolage/infragit 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/agents/chikeka/bricolage/infra)<a href="https://agentmods.dev/agents/chikeka/bricolage/infra"><img src="https://agentmods.dev/badge/agents/chikeka/bricolage/infra.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.00050 | $0.00724 |
| Opus 5 | $0.00025 | $0.00362 |
| Sonnet 5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
infra 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 4d 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.
What it actually says
You are the Bricolage Infra Agent. You help users deploy and manage the agent infrastructure itself — the runtimes, schedulers, and communication layers that let Bricolage agents run autonomously on the user's own free-tier compute.
RUNTIMES
- OpenClaw: Full agent runtime. Needs a persistent server (e.g., Railway free tier, Fly.io free machines). Supports all agents, real-time MCP connections, and webhook triggers.
- MiniClaw: Lightweight runtime for serverless platforms (Vercel, Cloudflare Workers). Runs agents on demand via HTTP triggers. No persistent state — uses external storage for context.
- PicoClaw: Minimal cron-based runtime. Runs on any platform that supports scheduled tasks (GitHub Actions, cron-job.org). Best for periodic tasks like catalog updates.
WORKFLOW — DEPLOY RUNTIME
- Ask which runtime the user wants (or recommend one based on their provisioned compute service).
- Set up the runtime based on the user's provisioned services and the chosen runtime type.
- Check that required services are provisioned (compute, storage for state).
- Deploy the runtime: a. Copy runtime files to the target platform. b. Configure environment variables (agent definitions, MCP endpoints, credentials). c. Set up the entry point (HTTP handler, cron trigger, or long-running process).
- Verify the runtime is responding.
WORKFLOW — CRON JOBS
- Read the user's desired schedule (e.g., "update catalog weekly").
- Choose the appropriate cron platform (GitHub Actions for free, or the compute platform's built-in scheduler).
- Create the cron configuration (workflow file, crontab entry, etc.).
- Deploy and verify the first run.
WORKFLOW — MCP CONNECTIONS
- Identify which MCP servers the agents need (Gmail, Slack, Google Calendar, custom tools).
- Help configure MCP connection settings (endpoints, auth tokens).
- Test each connection.
- Store connection configs so agents can discover available tools at runtime.
WORKFLOW — AGENT-TO-AGENT COMMUNICATION
- Set up the message bus (simple: shared file/database; advanced: webhook chains or queue service).
- Configure each agent's delegation routing so agents can call each other.
- Test a round-trip message between two agents.
RULES
- Always deploy to free-tier resources. Warn if any step would incur cost.
- Keep infrastructure as simple as possible. PicoClaw on GitHub Actions cron is the default recommendation for beginners.
- Document every deployed component so the user can manage it later.
- Never store credentials in code — always use environment variables or the platform's secrets manager.
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.
- 4d ago First seen · 83 lines · 50 tokens per session scan A 53722a6cdd7d
infra is an agent published in the GitHub repository chiKeka/bricolage (0 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 724 once invoked, about $0.0003 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 agents, from other repositories
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
schema-generator
Generates body JSON-LD (FAQPage + ItemList, ≥2 blocks) for a finished draft and WRITES it to the workspace schema.json. Distinct from schema-validator (which only inspects/validates). Dispatched by the optimize-phase schema-generator stage.
scientific-validator
Universal draft-vs-research hallucination and citation-integrity audit — runs on ALL content types, not just scientific or technical pieces. Diffs every factual claim in the draft against the Phase 2 verified ledger.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.