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.
git clone --depth 1 https://github.com/Floka-as/floka-marketplaceWrote 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/commands/floka-as/floka-marketplace/build)<a href="https://agentmods.dev/commands/floka-as/floka-marketplace/build"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/build/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.
<a href="https://agentmods.dev/commands/floka-as/floka-marketplace/build"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/build.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.02329 |
| Opus 5 | $0.00033 | $0.01164 |
| Sonnet 5 | $0.00013 | $0.00466 |
| Haiku 4.5 | $0.00007 | $0.00233 |
Grade A, and why
build 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 11d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The output is a single markdown file at .claude/board.md (project-level) or ~/.claude/board.md (user-level default), in the canonical format defined below. Users can hand-edit afterwards.
Step 0: Detect existing board
Check for .claude/board.md in the current project tree, then ~/.claude/board.md. If either exists and --refresh was not passed, ask the user once:
- "I see an existing board at
<path>. Replace it / add to it / cancel?"
If the user wants to add only, skip to Step 4 with their existing roster as context.
Step 1: Welcome and frame
Brief explanation. Keep it under 4 sentences:
"We're going to build your advisory board — a small set of operator personas tailored to your situation. I'll ask 4–5 questions, suggest some archetypes, and you'll pick the ones that fit. The end result is a markdown file you can edit any time."
Then proceed.
Step 2: The interview
Use AskUserQuestion for these. Batch into 1–2 calls (max 4 questions per call). Do not exceed 5 total questions.
Q1 — Stage / situation (single-select, with free-text fallback via "Other"):
- Pre-revenue / building first thing
- 1–10 customers, finding fit
- Scaling what's working
- Pivoting or repositioning
- Established business; tactical questions 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.
- 11d ago First seen · 246 lines · 66 tokens per session scan A 0ada501adff0
build is a command published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 2,329 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.