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 skills add Floka-as/floka-marketplace --skill boardgit 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/skills/floka-as/floka-marketplace/board)<a href="https://agentmods.dev/skills/floka-as/floka-marketplace/board"><img src="https://agentmods.dev/badge/skills/floka-as/floka-marketplace/board/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/skills/floka-as/floka-marketplace/board"><img src="https://agentmods.dev/badge/skills/floka-as/floka-marketplace/board.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.00143 | $0.01351 |
| Opus 5 | $0.00072 | $0.00675 |
| Sonnet 5 | $0.00029 | $0.00270 |
| Haiku 4.5 | $0.00014 | $0.00135 |
Grade A, and why
board 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 12d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Board
This skill helps the user build a personal advisory board — a set of operator/founder personas tailored to their situation — and then channels those personas on demand for strategic questions.
The board is not bundled. No advisors are shipped with this skill. The user composes their own board through /board:build, which interviews them, suggests archetypes, and produces a local board file. The skill then reads that file when running advisors.
The board file
Location (in priority order):
.claude/board.md(project-level — used when present in the current working directory tree)~/.claude/board.md(user-level default)
Format: human-readable markdown with a fixed structure (see commands/build.md for the canonical layout). Users can hand-edit, version-control, share, or fork their board file.
Activation triggers
This skill activates when the user:
- Runs any
/board:*command directly - Asks for strategic input on positioning, pricing, sales, GTM, content/distribution, building/shipping, hiring, delegation, runway/jump decisions, or general "what should we do about X" business questions
- Phrases a question as "What would [name] say…", "As [advisor]…", "Convene the board on…", "I need a [adjective] perspective on…"
Do not activate for pure technical execution, debugging, or coding tasks.
First-use protocol
Before any consultation command (invoke, meeting, pipeline) runs:
- Check for a board file (project, then user-level).
- If none exists, do not answer with a generic strategic take. Instead, say:
"I don't see a board built yet. Run
/board:buildto compose one — I'll interview you for ~5 minutes and we'll end up with a tailored roster. Or run/board:auditif you've created.claude/board.mdby hand." - After
/board:buildfinishes, automatically run/board:auditand surface gaps.
Modes of consultation
Once a board exists:
| Command | What it does |
|---|---|
/board:invoke <advisor> <topic> |
Single advisor responds in voice. Ends with 1–2 of their characteristic questions for follow-up. |
/board:meeting <topic> |
3–5 most relevant advisors weigh in, then a synthesis section names agreements and disagreements. |
/board:pipeline <topic> |
All board members in the pipeline order defined in their board file, producing a structured strategic brief. |
/board:build |
Interactive composer (re-runnable any time to refresh). |
/board:audit |
Evaluates the current board for gaps, overlaps, and bias-balance. |
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.
- 12d ago First seen · 107 lines · 143 tokens per session scan A 17d0a1dbbf68
board is a skill published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 143 tokens to every session and 1,351 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…