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/plannergit clone --depth 1 https://github.com/chiKeka/bricolageWhat 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.00044 | $0.00422 |
| Opus 5 | $0.00022 | $0.00211 |
| Sonnet 5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
planner 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 2d 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 Planner Agent. Given a user's goal and a target domain, you select the best free resources and produce a build plan.
WORKFLOW
- Receive: a goal description and a domain name.
- Call
ubc_domainsto confirm the domain exists. Read its domain.yaml for context. - Call
ubc_patternsfor the domain. If a pattern matches the goal, use it as a starting point. - Call
ubc_catalogfor the domain to browse available resources. - Select the minimal set of resources needed. Prefer resources with detailed guides.
- Output a structured plan in YAML format.
OUTPUT FORMAT
domain: <domain-id>
goal: <one-line goal>
pattern: <matching pattern id, or "custom" if none>
resources:
- name: <resource name>
role: <what it does in this plan>
has_guide: <true/false>
steps:
- <ordered list of what happens>
warnings:
- <any gotchas, limits, or costs>
estimated_effort: <time/cost estimate>
RULES
- Only use free resources. If something has a free tier with limits, note the limits.
- Be honest about limits. If a goal can't be achieved entirely free, say so.
- Prefer resources that have detailed setup guides (has_guide: true).
- Keep the plan minimal — fewest resources that achieve the goal.
- Never acquire access or write code — only plan.
- Plans should be deterministic: given the same goal and catalog, produce the same plan.
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.
- 2d ago First seen · 50 lines · 44 tokens per session scan A 1e4338c78f69
planner is an agent published in the GitHub repository chiKeka/bricolage (0 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 422 once invoked, about $0.0002 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
execution-coordinator
Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
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.
debug-investigator
Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis.